chore(release): correct version tagging and improve promotion flow#3866
Conversation
…okup Update promote-rc and get_latest_rc_tag to work with the new tag format that lacks a 'v' prefix. Add corresponding unit tests to verify the behavior.
…git.tag Update git.tag to require a commit_ref. Restructure promote-rc to verify pre-conditions before making modifications, and point the final tag directly to the RC's commit SHA. Update tests accordingly.
…motion comment Rename and optimize `resolve_issue_number` to search by title via `gh` using corrected repo/label globals. Post a comment on the tracking issue with release and BCR search links upon successful promotion, and use `shlex.join` for copy-paste friendly logging.
![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 refactors the release tool to support promoting release candidates directly to final releases without checking out the tag, while also improving GitHub tracking issue updates and switching to shlex.join for safer command logging. The review feedback highlights two critical issues: a potential TypeError due to changing get_open_tracking_issues to require a version argument when parameterless calls still exist, and an inconsistency where release candidates are still created with a 'v' prefix but searched for without it.
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.
Rename to `get_release_tracking_issue` with strict error raising, refactor commands to use it, and remove the 'v' prefix from RC tags. Factor out `list_issues` helper in `gh.py` and add missing unit tests.
Pull request was closed
Default to dry-run=True to prevent accidental promotions. Update existing tests and add a new dry-run success test.
2 participants
This change refactors the release promotion tool to ensure all pre-conditions are verified before making any modifications and automates post-promotion tracking updates. It also fixes a bug where the tool incorrectly assumed 'v' prefixes when identifying the latest release candidate and computing the final version tag.