releasing
Releases this package to npm and GitHub. Use when cutting a new version of @jkudish/jev-mcp, bumping versions, writing changelogs, publishing to npm, tagging releases, or troubleshooting a publish that did not go as expected.
How do I install this agent skill?
npx skills add https://github.com/jkudish/jev-mcp --skill releasingIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill outlines a standard software release workflow for the @jkudish/jev-mcp package, utilizing well-known services like npm and GitHub. It includes a mandatory human-in-the-loop approval gate for publishing and relies on standard development tools and environment-configured credentials.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Releasing @jkudish/jev-mcp
Two destinations, one gate. The agent stages the npm release; only Joey can approve it (passkey, npmjs.com Staged Packages tab). Everything else is mechanical and exact.
Sequence
- Bump
versionin package.json. Add a## <version>section to CHANGELOG.md with user-visible changes only. No internal task ids, no private names. - Sync the lockfile:
npm install --package-lock-only. A name or version mismatch between package.json and package-lock breaksnpm ciin CI. - Commit, push, and wait for CI green. Do not release from a red build.
- Stage the npm release:
npx npm@latest stage publish. Record the staged version and shasum. Staging uses the configured NPM_TOKEN credential and never needs 2FA. - STOP. Ask Joey to approve the staged package at npmjs.com (Staged Packages tab, passkey). This is the human gate; nothing ships without it.
- After approval, tag the exact commit that was packed in step 4, not HEAD,
which may have moved:
git tag -a v<version> <sha> -m "v<version>: summary"thengit push origin v<version>. - Create the GitHub release from that tag with the changelog section as notes
and the install command
npx -y @jkudish/jev-mcp. - Verify:
npm view @jkudish/jev-mcp version --prefer-onlinereturns the new version and the release page renders.
Rules and traps
- Staged publishing cannot create a brand-new package. The first version of
any new package must be published interactively by Joey with
npx npm@latest publish(browser passkey). Everything after that stages. - Registry propagation lags roughly 5 to 10 minutes after approval. A 404 from
npm viewornpxright after publish is propagation, not breakage. - npx caches failed resolutions. After a propagation window, remove
~/.npm/_npxbefore concluding the package is broken. - Tag, tarball, and registry version must agree to the byte. Docs that land after staging ship in the next release; retagging a published version is never correct.
- The npm package README comes from the tarball at stage time, not from GitHub HEAD.
- Never republish a version that already exists on the registry.
Verification checklist
- CI green on the release commit.
npx npm@latest stage listshowed the staged version and shasum.- Joey approved;
npm view @jkudish/jev-mcp version --prefer-onlinereturns it. - The tag points at the packed sha and the GitHub release exists on that tag.
- Repository: https://github.com/jkudish/jev-mcp
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/jkudish/jev-mcp/releasing">View releasing on skillZs</a>