Release routine and npm publish workflow - #15
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
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. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aba41e5ae4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ### Release | ||
|
|
||
| 1. Bump every version field (`package.json`, `plugin.json`, the three plugin manifests, the two `marketplace.json` files, `scripts/build-agents-md.js`, `skills/offcut-{review,audit,help}/SKILL.md`), then run: |
There was a problem hiding this comment.
When the next release follows this checklist, neither the listed edits nor either build script updates the hard-coded #v0.4.0 and --ref v0.4.0 examples earlier in this README; build-plugin-package.mjs only copies that README into the plugin package. The new release would therefore continue directing users to version 0.4.0, so include these pins in the bump checklist or generate and verify them automatically.
Useful? React with 👍 / 👎.
1 participant
Summary
--ref v0.4.0) and a four-step release routine in the README..github/workflows/publish.ymlto publish@skelvar/offcutto npmjs with provenance when a GitHub release is published.Test plan
npm pack --dry-runincludes bootstrap, install, scan, hooks, rules, skills, adapters, AGENTS.md, and the three plugin manifests; excludes bench/, docs/, tests/, plugins/offcut scan --helpprints scanner usage;~/.offcut/runtimewas not creatednode --test --test-reporter=tap tests/*.test.js→# fail 0testandoffcut-scanon this PRDo not merge until
NPM_TOKENis set for a later release (not 0.4.0).Made with Cursor