Solve version discrepancy in release #142
Merged
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.
Issue
v0.2.0
resulted in a version discrepancy -It is unclear why this happened but one change might be the
pip
version used bycibuildwheel
in GitHub runner. The releasev0.2.0
usedpip==25.0.1
whereasv0.1.0
usedpip==24.3.1
on the runners.Summary of changes
To get reproducible results, have added
_version.py
in the repo and used thedynamic
attribute in.toml
to get the version (as in the qBraid SDK).This eliminates the dependency on
setuptools_scm
0.2.1.dev0+g0fd2956.d20250214
matches the [4th option of Default Versioning Scheme in the docs] (https://setuptools-scm.readthedocs.io/en/latest/usage/)0fd2956
was tagged withv0.2.0
, EOL changes might have happened due to the newly added.gitattributes
fileSummary of changes
git reset
in the pre-build script to ensure that no uncommitted changes are passed into the build processno-guess-dev
value forversion_scheme
to ensure that nodev
suffixes are present in the version