Skip to content

[CNSL-2134] Add post-release pending deploy branch management #104

Open
linhcrl wants to merge 1 commit intocockroachdb:mainfrom
linhcrl:post-release-branch-management
Open

[CNSL-2134] Add post-release pending deploy branch management #104
linhcrl wants to merge 1 commit intocockroachdb:mainfrom
linhcrl:post-release-branch-management

Conversation

@linhcrl
Copy link
Copy Markdown
Contributor

@linhcrl linhcrl commented Apr 10, 2026

After a successful release (tag creation), the workflow now automatically manages pending deploy branches:

  • Determines the appropriate new pending deploy branch by comparing timestamps from commit trailers and live remote branches
  • Creates a new pending deploy branch if the previous one is outdated or if none existss
  • Retargets all open PRs from old pending deploy branches to the current one. (As of now, workflow does not resolve conflicts caused by this.)

This ensures that after each release, there's always a fresh pending deploy branch ready, and PRs are automatically pointed to the right target.

@linhcrl linhcrl force-pushed the post-release-branch-management branch from 8bbde80 to eefdec9 Compare April 10, 2026 13:47
@linhcrl linhcrl changed the title [CNSL-2134] Add pending deploy branch management to release workflow [CNSL-2134] Add post-release pending deploy branch management Apr 13, 2026
After a successful release (tag creation), the workflow now
automatically manages pending deploy branches:

- Finds the most recent merged PR with a pending-deploy-YYYYMMDD-hhmmss
  head branch to identify what the last pending deploy branch was
- Compares its timestamp with any current live pending deploy branch
- Creates a new pending deploy branch if a newer one was already merged
  to main (indicating the current live branch is stale), or if none exists
- Retargets all open PRs from old pending deploy branches to the current
  one. (As of now, workflow does not resolve conflicts caused by this.)

This ensures that after each release, there's always a fresh pending
deploy branch based on the latest main, and PRs are automatically pointed
to the right target.

Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
@linhcrl linhcrl force-pushed the post-release-branch-management branch from eefdec9 to aabd8e8 Compare April 13, 2026 15:20
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.

1 participant