馃懛 [poetry] Remove upper version bounds from dependencies #744
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
cjolowicz
added a commit
that referenced
this pull request
Dec 27, 2021
Dependabot updates version constraints in pyproject.toml even when the version constraint already covers the new version, leading to frequent merge conflicts because the global content hash in poetry.lock changes. As of #744, this project template no longer uses upper version bounds for its dependencies. As a result, we are now able to use the "lockfile-only" versioning strategy to upgrade dependencies, including major version bumps. This strategy prevents Dependabot from modifying pyproject.toml, putting an end to the frequent merge conflicts.
cjolowicz
added a commit
that referenced
this pull request
Dec 27, 2021
#746) Dependabot updates version constraints in pyproject.toml even when the version constraint already covers the new version, leading to frequent merge conflicts because the global content hash in poetry.lock changes. As of #744, this project template no longer uses upper version bounds for its dependencies. As a result, we are now able to use the "lockfile-only" versioning strategy to upgrade dependencies, including major version bumps. This strategy prevents Dependabot from modifying pyproject.toml, putting an end to the frequent merge conflicts.
cjolowicz
added a commit
to cjolowicz/cookiecutter-hypermodern-python
that referenced
this pull request
Dec 27, 2021
Dependabot updates version constraints in pyproject.toml even when the version constraint already covers the new version, leading to frequent merge conflicts because the global content hash in poetry.lock changes. As of cjolowicz/cookiecutter-hypermodern-python-instance#744, this project template no longer uses upper version bounds for its dependencies. As a result, we are now able to use the "lockfile-only" versioning strategy to upgrade dependencies, including major version bumps. This strategy prevents Dependabot from modifying pyproject.toml, putting an end to the frequent merge conflicts. Retrocookie-Original-Commit: cjolowicz/cookiecutter-hypermodern-python-instance@3082062
cjolowicz
added a commit
to cjolowicz/nox-poetry
that referenced
this pull request
May 16, 2022
Dependabot updates version constraints in pyproject.toml even when the version constraint already covers the new version, leading to frequent merge conflicts because the global content hash in poetry.lock changes. As of cjolowicz/cookiecutter-hypermodern-python-instance#744, this project template no longer uses upper version bounds for its dependencies. As a result, we are now able to use the "lockfile-only" versioning strategy to upgrade dependencies, including major version bumps. This strategy prevents Dependabot from modifying pyproject.toml, putting an end to the frequent merge conflicts. Retrocookie-Original-Commit: cjolowicz/cookiecutter-hypermodern-python-instance@3082062
cjolowicz
added a commit
to cjolowicz/nox-poetry
that referenced
this pull request
May 16, 2022
* 馃摝 [poetry] Remove version bound for CalVer dependency flake8-bugbear Retrocookie-Original-Commit: cjolowicz/cookiecutter-hypermodern-python-instance@acec7f4 * 馃摝 [poetry] Remove upper version bounds from dependencies * 馃摝 [poetry] Remove upper version bound for click * 馃摝 [poetry] Remove upper version bound for development dependencies * 馃摝 [poetry] Sort development dependencies Retrocookie-Original-Commit: cjolowicz/cookiecutter-hypermodern-python-instance@e4c2c71 * 馃懛 [dependabot] Reduce merge conflicts using the lockfile-only strategy Dependabot updates version constraints in pyproject.toml even when the version constraint already covers the new version, leading to frequent merge conflicts because the global content hash in poetry.lock changes. As of cjolowicz/cookiecutter-hypermodern-python-instance#744, this project template no longer uses upper version bounds for its dependencies. As a result, we are now able to use the "lockfile-only" versioning strategy to upgrade dependencies, including major version bumps. This strategy prevents Dependabot from modifying pyproject.toml, putting an end to the frequent merge conflicts. Retrocookie-Original-Commit: cjolowicz/cookiecutter-hypermodern-python-instance@3082062
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.
Remove upper bounds from the version constraints for both core and development dependencies.
There are two separate reasons for removing version caps:
The first point is treated in detail in the following articles:
For the second point, see dependabot/dependabot-core#4435.
See also #743 and #746