Backport release process to 2.20-stable #2947
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* use new candidate tasks for release management * update the release workflow * don't load candidate rake tasks if the file isn't there this prevents us from having to load submodules during the release process, just to pick up tasks that aren't needed. * Let the build task create the gem * bump spec/shared for candidate code update * use the push & workflow_dispatch triggers * add the product.yml file * fix typo in release.yml
There was a problem hiding this comment.
Pull Request Overview
This PR backports the release process changes from the master branch to the 2.20-stable branch, enabling automated patch releases for the 2.20 series. The changes modernize the release workflow by replacing the manual GitHub action approach with an automated process that triggers on PR merges.
- Updates GitHub workflow to use automated release candidate process with multi-job architecture
- Adds product configuration file for release automation
- Simplifies version file and build task implementation
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| spec/shared | Updates subproject commit reference for shared test utilities |
| product.yml | Adds product metadata configuration for automated release process |
| lib/mongo/version.rb | Removes license header and adds automation warning comment |
| Rakefile | Replaces build task warning with actual gem building functionality |
| .github/workflows/release.yml | Completely restructures workflow from manual to automated multi-job release process |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This ports the release process changes from the master branch to 2.20-stable, allowing us to make patch releases to the 2.20 series as easily as we do to the master branch.