chore(deps): update dependency bump-my-version to v1 #676
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.
This PR contains the following updates:
>=0.32.1
->>=1.0.1
Release Notes
callowayproject/bump-my-version (bump-my-version)
v1.0.1
Compare Source
Compare the full difference.
Fixes
Fix type hinting compatibility for 3.8. 9c2bb03
Replaced
list
withList
for type hints to ensure compatibility with earlier Python versions.v1.0.0
Compare Source
Compare the full difference.
Breaking Changes
New
v0.33.0
Compare Source
Compare the full difference.
Fixes
Fixed warnings in documentation. 782077d
Refactored PEP621 tests into a class. 2a4f12a
The tests are pretty much the same but renamed for clarity.
Fixed: allow omitting the current version in sample-config. 6b369fe
If the current version is explicitly left empty during the
sample-config
questionnaire, the resultingtool.bumpversion
tablenow lacks a
current_version
key, and will fall back to PEP 621project.version
(if not dynamic). The instruction text specificallyhints at this new functionality.
New
Add test for moveable tags. df787f1
New feature: retrieve and update the PEP 621 project version, if possible. 3032450
When determining the current version, and if
tool.bumpversion.current_version
is not set, attempt to retrieve theversion from
project.version
à la PEP 621. If that setting is notset, or if the version is explicitly marked as dynamically set, then
continue with querying SCM tags.
When updating the configuration during bumping, if we previously
successfully retrieved a PEP 621 version, then update the
project.version
field inpyproject.toml
as well. We always update,even if the true current version was read from
tool.bumpversion.current_version
instead ofproject.version
.The docs have been updated; specifically, the "multiple replacements in
one file" howto and the reference for
current_version
.The tests have been adapted: the new
pep621_info
property wouldotherwise trip up the old test output, and the
None
default would tripup the TOML serializer. Additionally, new tests assert that
project.version
(and correspondingly, thepep621_info
property) iscorrectly honored or ignored, depending on the other circumstances.
Other
[pre-commit.ci] pre-commit autoupdate. 59e8634
updates: - github.com/astral-sh/ruff-pre-commit: v0.9.6 → v0.9.7
Updates
v0.32.2
Compare Source
Compare the full difference.
Fixes
Fixed coverage issue. b0c46a3
Refactor SCMInfo and Config imports. 49995c6
Other
[pre-commit.ci] pre-commit autoupdate. b786638
updates: - github.com/astral-sh/ruff-pre-commit: v0.9.4 → v0.9.6
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.