Closed WadeBarnes closed 2 years ago
indy-plenum uses a more consistent approach to versioning (though more complicated). indy-node uses the same approach as indy-plenum
.
I think the problem lies here in L936: https://github.com/hyperledger/indy-sdk/blob/a1095be324d4fd6e678fdcb73476ee6d5130ba86/.github/workflows/main.yml#L934-L937
The Version is set via the environment variable PACKAGE_VERSION
.
But on the enduser side this variable isn't set and the version is set to the fallback from:
https://github.com/hyperledger/indy-sdk/blob/a1095be324d4fd6e678fdcb73476ee6d5130ba86/wrappers/python/setup.py#L4
Is it possible to store the env.publish version variable in a file and in the setup.py read the version from that file? The only problem i see with that is, that the version is set by the action but the file in the repository if tracked at all would be out of date.
The new packages to fix this issue start here:
Example message from pip (for indy-plenum):
This error is caused by an inconsistency in the package version and the version listed in the package's
setup.py
.The package version is set correctly by the build:
However the version in
setup.py
is not updated with the matching version number:The build process and/or code needs to be updated to set the code's version numbers consistently.