-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More robust version handling: Keep versions aligned. #30
Comments
Looked into the version update problem (version not updating in setup.cfg (see this example) where the repo in this state shows a setup.cfg of 0.0.28 while the tag and pypi are at 0.0.33. This is where update should happen, but it's not clear how the version that is computed two lines above is communicated to the update_setup_cfg function -- not to be confused with wads version of the same (and same name) function. It's clear that there is a print to return hack happening (which we'd really like to eliminate). Yes, it seems like (hack continues) the VERSION is put in a variable, put in the GITHUB_ENV, and then it is recuperated by update_setup_cfg |
Yet more. In this new project, the Validation passed, but ci failed with the following message.
|
We've had problems with versions (the opinion of tags, setup.cfg, and pypi) getting misaligned and causing havoc.
Good-enough solutions were implemented, but these are more to enable us to diagnose the problem (#11) and circumvent it (#29).
This issue is meant to diagnose the problem further, to see what kind of use actions lead to misalignment in the first place, and solution the problem at that level.
The text was updated successfully, but these errors were encountered: