chore(release): configure semantic-release to use main branch #581
Merged
Conversation
Update actions/checkout from v1 to v4 with fetch-depth: 0 to enable full git history access and persist-credentials: false for security.
Add explicit branch configuration to semantic-release config to ensure releases are only created from the main branch.
Replace @cablanchard/semantic-release with explicit semantic-release plugin configuration. Update semantic-release from v19 to v24 and add individual plugins for changelog, git, and github. Update Node.js version in CI workflow from 16 to 24.
cblanc
approved these changes
Jun 3, 2026
Member
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Member
|
🎉 This PR is included in version 2.6.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
3 participants
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.
Add explicit branch configuration to semantic-release config to ensure releases are only created from the main branch.