docs(agents): count reverts as release triggers - #89
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The one-line documentation correction is accurate against .releaserc.json and semantic-release's default revert-as-patch rule, with no code impact and no other docs needing the same change.
Review effort: Balanced
Findings: None
What changed in this PR
This PR updates AGENTS.md to add revert to the list of commit types that trigger an npm publish on main. It corrects an understatement in the agent guide's "Ways To Hurt Yourself" section so contributors (human and agent) understand that merging a revert commit also cuts a release.
I confirmed the correction is accurate:
.releaserc.jsonconfigures@semantic-release/commit-analyzerwith onlypreset: conventionalcommitsand no customreleaseRules, so the plugin's default release rules apply — and those defaults release apatchfor reverts.CLAUDE.mdis a symlink toAGENTS.md, so it stays in sync automatically.- The release-trigger list is enumerated only in
AGENTS.md;docs/DISTRIBUTION.mddescribes releases generically ("a releasable commit publishes"), so no sibling correction is required.
Changes:
- Added
revertto the enumerated release-triggering commit types in the "Merging publishes" note. - Reflowed the bullet's line wrapping to accommodate the added word.
| File | Description |
|---|---|
| AGENTS.md | Adds revert to the list of commit types that publish @putdotio/rokit to npm, matching semantic-release's default behavior |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The agent guide now counts reverts among the commits that publish to npm.
@semantic-release/commit-analyzerdefault rules release a patch for reverts, and.releaserc.jsonsets no custom rules, so "feat, fix, perf or breaking" understated what a merge publishes. Same correction Codex raised on the sibling Roku and Tizen guides.vp run checkpasses.Written by an agent (Claude Code, Opus 5.5)