@doki-land/nifty-skills 0.1.12 → 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.12"
25
+ "version": "0.1.14"
26
26
  }
@@ -41,7 +41,8 @@ nifty bump --version 0.0.3
41
41
  nifty bump --dry-run
42
42
  ```
43
43
 
44
- Aligns all `projects/crates/*/Cargo.toml` and `projects/packages/*/package.json` versions.
44
+ Aligns all `projects/crates/*/Cargo.toml` and every publishable `projects/packages/*/package.json` version. Packages
45
+ that are `private: true` or left out of `publish.packages` keep their current version.
45
46
 
46
47
  ## Repository policy (read first)
47
48
 
@@ -64,6 +65,11 @@ nifty trust --dry-run
64
65
  nifty trust
65
66
  ```
66
67
 
68
+ **Internal dependency specs**: publish rewrites `workspace:*` and `file:` specs to the version being published and
69
+ does **not** rewrite exact pins or ranges. Keep internal dependencies on `workspace:*`. A package whose exact pin
70
+ still points at an older version of another workspace package fails the publish preflight instead of silently
71
+ shipping a dependency on the previous release.
72
+
67
73
  **`--placeholder`**: for each publishable workspace package with **no version on the registry**, publish
68
74
  workspace contents as **`0.0.0`** (claim the name / prep Trusted Publisher). Packages that already exist on
69
75
  npm are skipped. Publishable means `private` is **not** set (or `false`) in `package.json`; dependents with a
@@ -83,6 +89,12 @@ nifty trust --only @doki-land/nifty-skills
83
89
  GitHub Actions OIDC can publish on the next tag. `nifty trust` uses `publish.packages` from `nifty.config.ts` when set
84
90
  (subset only — still respects `private`), otherwise all publishable workspace packages.
85
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
+
86
98
  Local auth: `NPM_TOKEN`, `--npm-token`, `--otp`, or `--totp-secret` (see `nifty publish --help`). Trust uses the
87
99
  registry API with bearer token from `NPM_TOKEN` or `~/.npmrc`. Add OTP/TOTP on 2FA accounts when the registry asks.
88
100
  Per the repository policy above, these paths are not used for real releases in `npm-tools` or VMZ-family repos.