Repository navigation
ci: stop hardcoding the release author, release README updates, and make samc621 code owner - #6
Merged
Merged
Conversation
…ake samc621 code owner - release.yml: the release commit is now authored and committed by whoever made the commit that triggered the release, not a fixed identity. - .releaserc.json: a docs(readme) commit now cuts a patch release, so README changes reach npmjs.com, and it is listed under Documentation in the notes. Other docs, ci and chore commits still do not release. - CODEOWNERS: @samc621 replaces @akarshtechsuite. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 0.2.2 🎉 The release is available on: 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.
What this does
The same release changes as agenttrailhq/guard#5, applied to Guardrails.
that triggered the release (the merge or push to
main), instead of the hardcodedakarshtechsuiteidentity.docs(readme):commit now cuts a patch release, so README changes reachnpmjs.com (npm only shows the README from the published package). It is listed under
"Documentation" in the release notes. Other
docs,ciandchorecommits still do not release.@samc621replaces@akarshtechsuite.Guard's #5 also pinned the changelog preset so release notes could generate. Guardrails already has
that fix (#5 here, shipped in 0.2.1), so it is not repeated.
Releases
This is a
ci:change, so merging it does not release anything by itself.Checked
docs(readme)gives a patch;feat,fixandperfgive a patch; breaking gives a minor; otherdocs,ci,choreand untyped commits give no release. The notes show the README entry andhide other docs and ci commits.
@agenttrail/guard@0.4.1with it.🤖 Generated with Claude Code