Releases: octue/django-twined
Releases · octue/django-twined
Widen django-gcp dependencies fully t avoid rapid development loop
<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! --> <!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. --> <!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required --> <!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. ---> <!--- START AUTOGENERATED NOTES ---> <!--- END AUTOGENERATED NOTES --->
Widen django-gcp dependency
Update to `uv`
Fix test matrix and update stack
Contents (#86)
Operations
- Update dev stack and tools consistent with django-gcp
- Update to use consistent ruff hooks
- Apply import sorting
- Revert accidental version bump
- Fix settings in ci environment
Testing
- Update test matrix
Style
- Conform to updated code format
Widen django-gcp range
Widen django-gcp dependency
<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! --> <!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. --> <!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required --> <!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. ---> <!--- START AUTOGENERATED NOTES ---> <!--- END AUTOGENERATED NOTES --->
Widen dependency range for django-gcp
<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! --> <!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. --> <!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required --> <!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. ---> <!--- START AUTOGENERATED NOTES ---> <!--- END AUTOGENERATED NOTES --->
FIX: Broken release tag
<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! --> <!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. --> <!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required --> <!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. ---> <!--- START AUTOGENERATED NOTES ---> <!--- END AUTOGENERATED NOTES --->
Update django dependencies
Contents (#79)
Dependencies
- Updating django dependencies
- updating dependency and version change
- Updating dependency & adding version
Publish to PyPI using trusted publisher
Contents (#78)
Operations
- Publish to PyPI using trusted publisher in
cdworkflow - Add
codeqlworkflow - Only run
ciandsemanticworkflows on non-draft pull requests, and additionally trigger them on "ready for review" event