Skip to content

PR-based release back-merge; fast-forward release flow - #19

Merged
w1ne merged 3 commits into
developfrom
chore/release-backmerge-fix
Jul 2, 2026
Merged

PR-based release back-merge; fast-forward release flow#19
w1ne merged 3 commits into
developfrom
chore/release-backmerge-fix

Conversation

@w1ne

@w1ne w1ne commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Follow-up to the CI-honesty changes in #17:

  • back-merge-develop direct-pushed a merge commit to the now-protected develop and failed GH006 on the v1.2.0 release. It now checks ancestry (no-op when main ⊆ develop) and opens a PR when a back-merge is genuinely needed.
  • RELEASE_STRATEGY.md documents the fast-forward promotion flow (git push origin origin/develop:main) that keeps main an exact subset of develop, and mentions the SBOM release assets.
  • Branched off merged main, so merging this PR also re-converges develop and main histories after the Release v1.2.0: CRA security package #18 merge commit.

🤖 Generated with Claude Code

w1ne and others added 3 commits July 1, 2026 14:11
Release v1.2.0: CRA security package
The old back-merge job direct-pushed a fresh merge commit to develop,
which protected-branch rules now reject (GH006 on the v1.2.0 release).
Releases fast-forward main to green develop SHAs, so the job is normally
a no-op; if main diverged it opens a PR instead of pushing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@w1ne
w1ne merged commit c5393e0 into develop Jul 2, 2026
3 checks passed
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