Skip to content

feat(deploy): create release-line branch on prod release for hotfixes (CPL-358) - #587

Open
GTC6244 wants to merge 3 commits into
mainfrom
feature/cpl-358-when-doing-a-production-release-the-one-that-looks-at-tags
Open

feat(deploy): create release-line branch on prod release for hotfixes (CPL-358)#587
GTC6244 wants to merge 3 commits into
mainfrom
feature/cpl-358-when-doing-a-production-release-the-one-that-looks-at-tags

Conversation

@GTC6244

@GTC6244 GTC6244 commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

The tag-triggered production release workflow (deploy-prod-1-propose.yml) now lands each released commit on a minor-version branch release/vX.Y via a new create-release-branch job, so all patch releases on a line share one branch and hotfixes to a shipped version get a stable home that never moves as main advances. The job runs only on tag pushes and only fast-forwards an existing branch (never force-pushes), so hotfix commits already on a line are never discarded. The hotfix workflow is documented in architectureDocs/deployment/vm-code-upgrade.md.

🤖 Generated with Claude Code

GTC6244 and others added 2 commits July 17, 2026 12:00
… (CPL-358)

The tag-triggered prod release (deploy-prod-1-propose.yml) now lands each
released commit on a minor-version branch release/vX.Y via a new
create-release-branch job. All patch releases on a line share one branch,
giving hotfixes to a shipped version a stable home that never moves as main
advances. The job only fast-forwards an existing branch (never force-pushes),
so hotfix commits already on the line are never discarded. Documented the
hotfix workflow in architectureDocs/deployment/vm-code-upgrade.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…safe

Address PR review: git fetch always writes FETCH_HEAD, but the
origin/$BRANCH remote-tracking ref may not exist under actions/checkout's
narrow fetch refspec, so base the fast-forward ancestor check on FETCH_HEAD.
Update the hotfix docs to fetch before switching so the commands work on a
fresh clone.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@GTC6244
GTC6244 requested review from a team and Copilot July 20, 2026 18:46

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

This PR updates the production, tag-triggered deployment workflow to maintain a stable “release-line” branch per minor version (e.g., release/v1.2) so hotfixes for shipped versions have a consistent branch target as main continues to move forward, and documents the hotfix workflow.

Changes:

  • Add a create-release-branch job to .github/workflows/deploy-prod-1-propose.yml to create/fast-forward release/vMAJOR.MINOR on tag pushes.
  • Document the release-line and hotfix flow in architectureDocs/deployment/vm-code-upgrade.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
architectureDocs/deployment/vm-code-upgrade.md Documents how release-line branches are created and how to ship hotfix patch releases safely.
.github/workflows/deploy-prod-1-propose.yml Adds a new job that creates/advances release/vX.Y for each tagged prod release (fast-forward only).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/deploy-prod-1-propose.yml
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.

2 participants