Skip to content

docs(release): Modify release script to include exact gh commands#451

Merged
heyitsaamir merged 1 commit into
mainfrom
aamirj/release-md-fixes
Jun 8, 2026
Merged

docs(release): Modify release script to include exact gh commands#451
heyitsaamir merged 1 commit into
mainfrom
aamirj/release-md-fixes

Conversation

@heyitsaamir

@heyitsaamir heyitsaamir commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

In the previous doc, the instruction was to do main -> release. But since release and main have different histories, there were many merge conflicts that had to be resolved. To do this, we had to use -s ours when merging.
Since this needs to be done on our machine anyway (and also because version.json also needs to be modified), I updated the doc to just be exact commands that need to be run so agents can help us execute the release workflow quickly.

Copilot AI review requested due to automatic review settings June 5, 2026 23:01
@heyitsaamir heyitsaamir force-pushed the aamirj/release-md-fixes branch from b7045d4 to 1d2e4b3 Compare June 5, 2026 23:04

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates RELEASE.md to document the actual long-lived release branch workflow, including a recommended preparation approach that avoids recurring merge-base/phantom-conflict issues caused by prior squash merges.

Changes:

  • Clarifies that release is long-lived and releases are prepared by bringing main into release via a PR (rather than creating a new release branch).
  • Documents a git merge -s ours origin/release workflow to re-establish clean merge ancestry going forward.
  • Refreshes version examples to 2.0.13 and replaces tac with a portable awk one-liner.

Comment thread RELEASE.md Outdated
Comment thread RELEASE.md Outdated
Comment thread RELEASE.md Outdated
Comment thread RELEASE.md
@heyitsaamir heyitsaamir force-pushed the aamirj/release-md-fixes branch 3 times, most recently from ac662fb to 4aafe87 Compare June 5, 2026 23:10
- Clarify that release is long-lived, not created fresh per release
- Document the -s ours pattern to avoid phantom conflicts from prior
  squash-merges
- Update example versions to current (2.0.13)
- Replace tac (not on macOS) with awk one-liner
@heyitsaamir heyitsaamir force-pushed the aamirj/release-md-fixes branch from 4aafe87 to f501314 Compare June 5, 2026 23:12
@heyitsaamir heyitsaamir changed the title docs(release): correct workflow for long-lived release branch docs(release): Modify release script to include exact gh commands Jun 5, 2026
@heyitsaamir heyitsaamir merged commit eaec265 into main Jun 8, 2026
4 checks passed
@heyitsaamir heyitsaamir deleted the aamirj/release-md-fixes branch June 8, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants