Clarify release branch and tagging workflow - #209
Conversation
Co-authored-by: Codex <noreply@openai.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThis PR updates the release runbook with new snapshot versioning, branch creation, RC and GA procedures, and changelog guidance. It adds ChangesRelease Documentation and Config Update
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/CI.md:
- Around line 162-167: Update the release command examples around the git fetch
steps to fail immediately when repository refresh commands fail, preventing
subsequent operations from using stale refs. After displaying the source SHA,
capture and compare it with the SHA resolved for the pushed release branch or
created tag, and stop with an error if they differ; apply the same validation to
both command sequences.
- Around line 229-239: Update Step 9 in CI.md to add a preflight that fetches
and prunes remote tags, then verifies both refs/tags/vPREVIOUS.GA and
refs/tags/vX.Y.Z before running the git diff and git log comparisons. Keep the
existing comparison commands and release sequencing unchanged.
- Around line 219-221: Update the “Iterate” release instructions to require that
<sha> identify a single-parent commit, or explicitly document how to select the
correct mainline parent when cherry-picking a merge commit; do not prescribe -m
1 without establishing that parent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 36ce4d19-2a40-4994-8b69-e4bdf2ef65b5
📒 Files selected for processing (2)
.github/CI.md.github/release.yml
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Summary
release/X.Y.0from a reviewedmaincommit.mainbuilds and how fixes flow to release branches.Validation
.github/CI.mdand.github/release.yml.AI-assisted: Created with Codex/GPT at the user's request.
Summary by CodeRabbit
Documentation
Chores