Repository navigation
ci: Release with semantic-release - #17
Merged
Merged
Conversation
Same setup as the other brainbits packages, but: - only runs after a successful Build of a push to main - semantic-release version pinned - explicit token permissions Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 8.0.2 🎉 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
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.
Changes
.releaserc,.github/workflows/release.yaml), same setup as the other brainbits packages (commit-analyzer,release-notes-generator,github, tag format withoutv)Buildof a push tomain(workflow_run), so failing tests are never released25.0.9instead of always pulling the latestcontents,issues,pull-requests: write); the build workflow stays read-onlyCLAUDE.md: document how commit types map to versionsExpected result
Commits since
8.0.1containfix:but nofeat:/BREAKING CHANGE, so merging this PR should create 8.0.2 (tag + GitHub release), including everything from #15. Packagist picks up the tag via webhook.The release workflow only runs once it is on
main, so it is first exercised by merging this PR.🤖 Generated with Claude Code