build: migrate from bump-my-version to versioningit #1832
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
egparedes
changed the title
egparedes
force-pushed
the
move-to-versioningit
branch
2 times, most recently
from
11a6ed9 to
da406e7
Compare
15 tasks
egparedes
force-pushed
the
move-to-versioningit
branch
2 times, most recently
from
3ca0095 to
9f10bc6
Compare
egparedes
force-pushed
the
move-to-versioningit
branch
from
9f10bc6 to
c610259
Compare
havogt
reviewed
Jan 31, 2025
Comment on lines
-16
to
23
|
|
||
| 4. Commit the changes with the following message: | ||
| 4. Tag the previous commit with the exact `v{M}.{m}.{p}` tag to update the version number and push all the changes: | ||
|
|
||
| ```bash | ||
| $ git commit -m 'Releasing {M}.{m}.{p} version.' | ||
| $ git tag v0.1.2 # replace by the right version tag | ||
| $ git push origin master | ||
| $ git push --tags origin | ||
| ``` |
There was a problem hiding this comment.
This is implicit in the next step.
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.
Use
versioningitas asetuptoolsplugin to use the information in git tags as source of truth for the distribution package versioning. This should allow for a much finer version specification, since essentially every commit defines a new version, even when installed in editable mode. Some other important packages are following similar approaches (e.g. jax).TODO:
pyproject.toml export-substto.gitattributesas explained in thegit-archivemethod documentation.gitrepo