chore(release): automate multi-version backports and support direct patch promotion#3936
Conversation
Added backport-prepare and backport-create-releases commands to automate backporting PRs to multiple active release branches. Renamed and refactored promote-rc to promote to support direct tagging of patch releases on the branch head, bypassing RC verification.
rickeylev
changed the title
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces automated patch releases to multiple versions by adding the backport-prepare and backport-create-releases subcommands, and refactors the promote-rc command to promote to support direct patch releases from the branch head. Feedback on the implementation highlights Windows compatibility issues in gh.py where tempfile.NamedTemporaryFile is kept open during CLI execution, leading to file locking errors. Additionally, a bug was identified in backport_prepare.py where version comparisons fail if a patch version is specified (e.g., 1.7.0 instead of 1.7), which can be resolved by slicing the version list to compare only the major and minor components.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
Adds automated workflow and tooling support for multi-version backports and support direct patch release promotion.
Previously, backports required manual preparation and tracking across multiple branches, and patch releases were promoted as RCs instead of direct patch releases.
This change: