[ci] Create pre-release workflow #13513
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.
Description
This CI job can only be run manually; has a text input for version number and a checkbox for whether it uses Beta channel (beta on the "Early Stable Release" day has always been the same build number as the Stable Release several days later).
Running this on current code with the current Beta CDP (122)
looks like this: https://github.com/titusfortner/selenium/actions/runs/7661130480/job/20880319510
and results in this:
titusfortner#58
Motivation and Context
The previous release process didn't handle the Rust version -> SM build -> prep process correctly.
There's no good way to do that with a Rake task, so I created this github workflow to do it.
This is also nice because you can kick it off and it will automatically run the tests.
While the tests are running:
gh pr checkout 12345
), make the updates to the changelogs and push them back to the pr and merge itThen all that is left is to run:
./go all:release
and it should finish doing everything