You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently to update version using CD 2 commands are required:
git tag v2.0.1 main
git push origin v2.0.1
But it causes issues when versions are desynchronized. For example as in this commit: label version is 2.5.3, while the pyproject.toml version is 2.5.2.
Since it's required to have a version in pyproject.toml and it's not flexible, while git tag is optional, I suggest to take version from pyproject.toml and apply it as a git tag. It can be done in github actions, but it would require some workarounds. It's most easily done via git hooks, but they are not automatically shareable for good reasons.
It will allow us to avoid desync issues and streamline version bump for new, as well as existing, contributors.
The text was updated successfully, but these errors were encountered:
Privat33r-dev
changed the title
Make single source of truth for the version
[CD] Make single source of truth for the version
May 1, 2024
Currently to update version using CD 2 commands are required:
But it causes issues when versions are desynchronized. For example as in this commit: label version is
2.5.3
, while thepyproject.toml
version is2.5.2
.Since it's required to have a version in
pyproject.toml
and it's not flexible, while git tag is optional, I suggest to take version frompyproject.toml
and apply it as agit tag
. It can be done in github actions, but it would require some workarounds. It's most easily done via git hooks, but they are not automatically shareable for good reasons.It will allow us to avoid desync issues and streamline version bump for new, as well as existing, contributors.
The text was updated successfully, but these errors were encountered: