Repository navigation
Add a v1 npm deprecate step to the release skill - #2968
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: cliffhall <cliff@futurescale.com>
4 tasks
There was a problem hiding this comment.
🟡 Changes recommended
The handoff’s deprecation commands depend on MSG being set in the same shell, so running them independently can remove deprecation notices instead of applying them.
1 open issue
What changed in this PR
Adds a manual npm deprecation step to the v1 release procedure, addressing #2954 so newly published v1 versions receive the existing deprecation notice.
Changes:
- Documents exact-version deprecation for all four packages, with maintainer-run commands and two-factor authentication guidance.
- Adds warnings about version ranges and empty messages, plus verification of v1 notices and unaffected v2 releases.
- Adds deprecation to the release issue checklist and renumbers the advisory release-notes step.
| File | Description |
|---|---|
.claude/skills/release/SKILL.md |
Extends the v1 release procedure with manual deprecation and verification instructions. |
Review effort: Balanced
A shell variable is empty in a fresh ! invocation, which would lift the notice instead of applying it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: cliffhall <cliff@futurescale.com>
Member
Author
|
Copilot review loop closed — exit: clean round (round 2, no inline comments, no suppressed findings).
|
4 tasks
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.
Closes #2954
Adds v1-6. Deprecate the version just published to the
releaseskill's v1 flow, after v1-5 (Verify). The old v1-6 (release notes for unpublished advisories) becomes v1-7; nothing outside the skill referenced the step numbers.The new step covers each acceptance criterion:
@modelcontextprotocol/{inspector,inspector-cli,inspector-client,inspector-server}@X.Y.Z.<2.0.0matches2.0.0-rc.1/2/3; the safe spelling is<2.0.0-0.npm view …@<PREVIOUS> deprecated, and stated verbatim (checked against 1.0.3 on npm).EOTP; an agent stops and hands over the four commands (! npm deprecate … --otp=<code>); fresh TOTP codes per command.npm view … deprecated --prefer-onlinefor all four, plus a check that2.0.0-rc.1..3andlateststay un-deprecated.v1-1 also now says to list the deprecate step in the v1 release issue's checklist, per the issue's optional suggestion.
Only the skill body changed.
releaseisdisable-model-invocation: trueand its description is untouched, so noskills:evalre-run is needed.npm run verify:skillsandnpm run local:gatepass.🤖 Generated with Claude Code