Repository navigation
ci: switch release flow to target develop directly - #67
Merged
Merged
Conversation
Release Please now triggers on push to develop and creates release PRs against develop. Tags are created on develop commits; the existing on:push:tags trigger fires the publish pipeline from there. This eliminates the develop→main merge dance, merge conflicts, and version bump mismatches that plagued every release cycle. main becomes a read-only mirror updated manually after each stable release.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every release cycle hit the same issues:
Root cause: Release Please scans main's first-parent linear history. Merging develop into main via a merge commit hides the conventional commits inside the second parent — Release Please never sees them.
Fix (Option B)
release-please.yml: trigger onpush to develop,target-branch: developrelease-please-config.json:target-branch: developNew release flow
develop(unchanged)chore: release X.Y.ZPR targeting developmainbecomes a stable mirror — updated manually after each release if desired.