Updating django dependencies #79
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thclark
reviewed
Nov 26, 2024
pyproject.toml
Outdated
| django-gcp = ">=0.11.5,<0.13" | ||
| django-gcp = "^0.13.0" |
There was a problem hiding this comment.
@Anusha0521 this is now quite restrictive. In semantic versioning, django-gcp moving from 0.11 to 0.12 or 0.13 represents a breaking change. A user of django-twined who wants to update will now also have to update django-gcp, migrating across any breaking changes. Forcing them to do that right now is a bit rough!
This PR doesn't make any change to the way in which django-gcp is used so it should still be backward compatible to >=0.11.5
thclark
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contents (#79)
Dependencies