Point npm latest at @rc (local / no CI token)

Maintainer break-glass alternative to the release workflow’s NPM_TOKEN path. The root script pnpm point-latest-at-rc runs scripts/point-latest-at-rc.js --from-rc --local so npm dist-tag uses your logged-in session. Write commands inherit stdin/stdout so npm can prompt for OTP when 2FA is on auth-and-writes (run from a real TTY). Prefer a single OTP for the whole run via --otp <code> or NPM_CONFIG_OTP — otherwise npm prompts once per package (~12 times). Trusted Publishing still covers publish; this skill only covers dist-tag.

Do not remove or disable the CI promote job. Prefer CI promote_rc_to_latest when secrets.NPM_TOKEN works; use this only when CI cannot (or as emergency retag).

Preconditions

1. Repo root on a branch with .changeset/pre.json → "mode": "pre", "tag": "rc" (same gate as CI).
2. Packages already published under @rc (e.g. 1.0.0-rc.1).
3. npm user who can write dist-tags on @arkenv/* and arkenv (npm login if needed).

Steps

# 1. Confirm auth
npm whoami

# 2. Optional dry-run (lists dist-tag commands; still resolves @rc)
pnpm point-latest-at-rc --dry-run

# 3. Retag (no NPM_TOKEN) — preferred: one OTP for all packages
pnpm point-latest-at-rc -- --otp <code-from-authenticator>
# or: NPM_CONFIG_OTP=<code> pnpm point-latest-at-rc

Without --otp / NPM_CONFIG_OTP, run from a real TTY and expect one interactive OTP prompt per package.

Verify

npm view arkenv dist-tags
npm view @arkenv/core dist-tags
npm view @arkenv/agent-plugin dist-tags

Expect latest and rc both at the same 1.0.0-rc.n.

Smoke (after retag)

• Bare npx arkenv init
• @arkenv/core + arktype in a fresh Node app
• One framework example if time allows

Failures

Related

• Docs: docs/RC_CHECKLIST.md §C (CI primary; local break-glass)
• CI: .github/workflows/release.yml → promote_rc_to_latest (needs NPM_TOKEN; leave in place — primary path)
• Script help: node scripts/point-latest-at-rc.js --help