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
There should be some process that either automates switching _version_extra in version.py from dev to '' before publishing a release, or enabled editing of the saltproc/version.py file once the release is published. Both would be nice.
This issue can be closed when a PR that adds the described functionality exists, AND when the version.py under the v0.4.0 tag has the correct version.
Some ideas on how to do this:
Make the next-minor-release.yml workflow trigger from closing a milestone, and add functionality to change version.py as well as publishing the current draft release. We will also document this in the Developer guide.
Expected behavior
The version for the 0.4.0 release should be
0.4.0
Describe the bug
The version is actually
0.4.dev-0
To Reproduce
Steps to reproduce the behavior:
saltproc/version.py
under the v0.4.0 tagSystem Specifications:
How can this issue be closed?
There should be some process that either automates switching
_version_extra
inversion.py
fromdev
to''
before publishing a release, or enabled editing of thesaltproc/version.py
file once the release is published. Both would be nice.This issue can be closed when a PR that adds the described functionality exists, AND when the
version.py
under thev0.4.0
tag has the correct version.Some ideas on how to do this:
next-minor-release.yml
workflow trigger from closing a milestone, and add functionality to changeversion.py
as well as publishing the current draft release. We will also document this in the Developer guide.version.py
as needed after publishing a releaseversion.py
that must be merged before publishing the releaseThe text was updated successfully, but these errors were encountered: