docs: pack:verify is not a local:gate stage; name it as its own release step (#2380)
The release skill's step 2a claimed pack:verify runs inside local:gate; it does not. Make it an explicit step there, and correct pre-push-gate's claim that CI never runs it (the publish job does, on a published release). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
parent
de2cbaeeaf
commit
3463304fbb
1 changed files with 15 additions and 6 deletions
|
|
@ -207,6 +207,8 @@ it — the split is the design.
|
|||
|
||||
`npm run pack:verify` builds, packs the real tarball, installs it into a clean
|
||||
throwaway consumer, and drives the installed `mcp-inspector` bin end to end. It
|
||||
needs **network access**, so it is a local/release check and is in neither
|
||||
`local:gate` nor CI. Run it when touching packaging (the `files` allowlist,
|
||||
a bundler `external` list, anything read from disk at runtime).
|
||||
needs **network access**, so it is a local/release check: it is **not** a
|
||||
`local:gate` stage, and CI runs it only in the `publish` job on a published
|
||||
GitHub Release — never on a push or PR. Run it when touching packaging (the
|
||||
`files` allowlist, a bundler `external` list, anything read from disk at
|
||||
runtime), and as its own step when cutting a release (the `release` skill).
|
||||
|
|
|
|||
Loading…
Reference in a new issue