ci: add npm-deprecate utility workflow (reuse cd.yml's NPM_TOKEN)#294
Merged
Conversation
npm now mandates 2FA-or-bypass-token for all write operations. The heznpc account has no 2FA configured, so local `npm deprecate` hard-403s with no OTP prompt — both from this machine and from the owner's interactive terminal. Meanwhile cd.yml already publishes with secrets.NPM_TOKEN (bypass-2FA), proven live by the SLSA provenance attestation on airmcp@2.12.0. Add a workflow_dispatch utility that runs `npm deprecate` (or un-deprecate) with that existing secret, in the place the secret already lives — no fresh token on a laptop. Inputs flow through env: and are referenced only as "$VAR" (no injection surface); dispatch requires repo write access. First use: deprecate the two pre-rename zombie packages `@heznpc/imcp` and `iconnect-mcp` pointing installs at `airmcp` — the npm leg of the brand-footprint cleanup (registry leg done: io.github.heznpc/airmcp active, iconnect deprecated).
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
1 participant
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.
npm now mandates 2FA-or-bypass-token for all write operations. The heznpc
account has no 2FA configured, so local
npm deprecatehard-403s with no OTPprompt — both from this machine and from the owner's interactive terminal.
Meanwhile cd.yml already publishes with secrets.NPM_TOKEN (bypass-2FA), proven
live by the SLSA provenance attestation on airmcp@2.12.0.
Add a workflow_dispatch utility that runs
npm deprecate(or un-deprecate)with that existing secret, in the place the secret already lives — no fresh
token on a laptop. Inputs flow through env: and are referenced only as "$VAR"
(no injection surface); dispatch requires repo write access.
First use: deprecate the two pre-rename zombie packages
@heznpc/imcpandiconnect-mcppointing installs atairmcp— the npm leg of the brand-footprintcleanup (registry leg done: io.github.heznpc/airmcp active, iconnect deprecated).