ci(release): switch release-trigger branch to dev#12
Merged
Conversation
przemarzec
force-pushed
the
chore/release-trigger-to-dev
branch
from
5afa68c to
77dbddf
Compare
przemarzec
changed the title
semantic-release now fires on push to dev. main becomes a stable mirror that inherits the tagged release-commit via a regular forward-merge from dev after each release. This aligns the release flow across the project and removes the deviation in which main was the publisher branch. Files: - .releaserc.json: branches main -> dev - .github/workflows/release.yml: trigger main -> dev; publish job checkout ref main -> dev; header comment updated - CLAUDE.md: branching section rewritten so dev is the release-trigger and main is a stable mirror; direct release/* -> main is not used
przemarzec
force-pushed
the
chore/release-trigger-to-dev
branch
from
77dbddf to
7619127
Compare
|
🎉 This PR is included in version 0.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Switch the release-trigger branch from
maintodevso the whole flow isfeature/* -> release/vX.Y.Z -> dev -> main, consistent across the project..releaserc.json: semantic-releasebranches->dev.github/workflows/release.yml: trigger on push todev; publish job checks outdev; header comment updatedCLAUDE.md+BRANCHING.md: branching docs corrected ?devis the release-trigger (tag + publish created ondev),mainis a stable mirror updated by forward-merge fromdev; arelease/*branch is never merged intomaindirectlyNo runtime/behaviour change to the package. Dormant until the next release.