Repository navigation
ci: fix releases, stop hardcoding the release author, and make samc621 code owner - #5
Merged
Merged
Conversation
… identity Pin conventional-changelog-conventionalcommits to ^9.3.1. Version 10 needs conventional-changelog-writer 9, but @semantic-release/release-notes-generator resolves writer 8, so the next release would fail in generateNotes before bumping the version. The guardrails repository made the same fix. Release a patch for docs(readme) commits, so README changes reach the npm page, and list them under Documentation in the release notes. Other docs commits still do not release. Author release commits as Samuel Corso, using his GitHub noreply address. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Take GIT_AUTHOR_* and GIT_COMMITTER_* from the commit that triggered the release (github.event.head_commit.author) instead of a hardcoded identity. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
loveneeshdhir
changed the title
loveneeshdhir
requested review from
samc621
and removed request for
akarshtechsuite
October 2, 2026 19:44
Request reviews from Samuel Corso instead of the previous developer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
loveneeshdhir
changed the title
|
🎉 This PR is included in version 0.4.1 🎉 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 changes
Fixes to the release pipeline, found while checking how versions get bumped, plus a code owner update.
1. The next release would fail. This fixes it.
conventional-changelog-conventionalcommitswas on^10.4.0, which needsconventional-changelog-writer9.@semantic-release/release-notes-generatorresolves writer 8,so the next
feat,fixorperfmerge would crash ingenerateNotes, before the version isbumped or anything is published. Nothing has triggered a release since the switch to
semantic-release, which is why this hasn't shown up yet. This pins the preset to
^9.3.1, thesame fix the guardrails repository shipped in agenttrailhq/guardrails#5.
2.
docs(readme):commits now release a patch.The README on npmjs.com comes from the published package, so README changes only reach npm with a
release. A commit typed
docs(readme): …now triggers a patch release and appears underDocumentation in the release notes and CHANGELOG. Other
docs:commits still do not release,and every other rule is unchanged (
feat,fix,perf→ patch; breaking → minor).3. Release commits are no longer authored by a fixed identity.
release.ymlhardcoded the previous developer as the author and committer of every releasecommit. It now takes both from the commit that triggered the release
(
github.event.head_commit.author), so a release is attributed to whoever merged or pushed tomain. On the last release run that would have been "Akarsh A S", who made that push.4. Samuel is the code owner.
.github/CODEOWNERSnamed the previous developer, so every PR requested his review. It now names@samc621. GitHub reports no errors in the new file.
How I checked it
@semantic-release/commit-analyzerand@semantic-release/release-notes-generatoragainst this config:docs(readme):→ patch;docs:,docs(contributing):,ci:,chore:and unprefixedcommits → no release;
feat:,fix:,perf:→ patch;feat!:→ minor.docs(readme)under Documentation and otherdocsandcicommits hidden.
maintoday, the unchanged config fails ingenerateNotes; with the pin it renders.pnpm install --frozen-lockfile,biome checkandcspellpass on the changed files.Notes
ci:change, so it does not release by itself.docs(readme): …title to publishthe new README as 0.4.1. That release would also ship
2c602b7("Update the vendoredrule-matching engine"), which is on
mainbut not yet on npm.🤖 Generated with Claude Code