@doki-land/nifty-skills 0.1.13 → 0.1.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -22,5 +22,5 @@
22
22
  "typecheck": "node -e \"console.log('docs-only skill package')\""
23
23
  },
24
24
  "type": "module",
25
- "version": "0.1.13"
25
+ "version": "0.1.14"
26
26
  }
@@ -89,6 +89,12 @@ nifty trust --only @doki-land/nifty-skills
89
89
  GitHub Actions OIDC can publish on the next tag. `nifty trust` uses `publish.packages` from `nifty.config.ts` when set
90
90
  (subset only — still respects `private`), otherwise all publishable workspace packages.
91
91
 
92
+ **Stale trust records**: a record can list the right repo/file/env yet be bound to an outdated provider identity on the
93
+ registry side (renamed/transferred repos, repos created under immutable OIDC subjects). The symptom is the OIDC publish
94
+ failing with `ENEEDAUTH` while the workflow and config look correct. Repair without any npm CLI: **`nifty trust --recreate`**
95
+ revokes every existing record for each package and creates a fresh one (fully non-interactive with `NPM_TOKEN` plus
96
+ `NPM_TOTP_SECRET` or `--otp`).
97
+
92
98
  Local auth: `NPM_TOKEN`, `--npm-token`, `--otp`, or `--totp-secret` (see `nifty publish --help`). Trust uses the
93
99
  registry API with bearer token from `NPM_TOKEN` or `~/.npmrc`. Add OTP/TOTP on 2FA accounts when the registry asks.
94
100
  Per the repository policy above, these paths are not used for real releases in `npm-tools` or VMZ-family repos.