Skip to content

Conversation

@HereThereBeDragons
Copy link
Contributor

cherry-pick from main: 8834ca3

Allows to promote .tar.gz and wheels from release candidate to release (e.g. 7.10.0rc1 --> 7.10.0). Can work on a single file, partial matches or entire directory.

Creates new files for the promotion. Has an option to delete the old prerelease version on successful promotion.

As we have a few custom files that also contain the version, added a modified third-party change_wheel_version.py to be able to also change the version in those non-standard files inside the wheel.

Works on Windows and Linux. Includes a promotion test.

Issue #1891

Allows to promote .tar.gz and wheels from release candidate to release
(e.g. 7.10.0rc1 --> 7.10.0). Can work on a single file, partial matches or
entire directory.

Creates new files for the promotion. Has an option to delete the 
old prerelease version on successful promotion.

As we have a few custom files that also contain the version, added a
modified third-party `change_wheel_version.py` to be able to also 
change the version in those non-standard files inside the wheel.

Works on Windows and Linux. Includes a promotion test.

Issue #1891

---------

Co-authored-by: Scott Todd <[email protected]>
@ScottTodd ScottTodd changed the title Python script to promote a version from prerelease to release (#1973) [release/7.10] Python script to promote a version from prerelease to release (#1973) Nov 25, 2025
Copy link
Member

@ScottTodd ScottTodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This cherry-pick doesn't look essential, but okay.

We could also run this script from main instead of from the release branch.

@HereThereBeDragons
Copy link
Contributor Author

i was thinking the same and then i thought maybe for history-tracking it might be good to also have the version we will use for this release also on the release branch? what do you think?

Base automatically changed from release/therock-7.10 to users/arravikum/release_changes7.10 November 26, 2025 15:33
@ScottTodd
Copy link
Member

Up to you. In general I want to limit the number of commits on release branches, but having a solid audit trail for releases is important too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: TODO

Development

Successfully merging this pull request may close these issues.

3 participants