@doki-land/nifty-skills 0.1.11 → 0.1.13

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.11"
25
+ "version": "0.1.13"
26
26
  }
@@ -50,7 +50,7 @@ Global flag: `-C, --cwd <dir>`.
50
50
  ```text
51
51
  projects/crates/ # Rust libraries + nifty-napi
52
52
  projects/packages/ # @doki-land/nifty + platform @doki-land/nifty-*
53
- scripts/ci/ # bind-publish-tag.mjs, require-ci-success.mjs, nifty.mjs
53
+ scripts/ci/ # bind-publish-tag.mjs, check-rust-dependency-policy.mjs, require-ci-success.mjs
54
54
  ```
55
55
 
56
56
  Do **not** confuse npm-tools `legion` / Valkyrie with Nifty. Nifty is independent Node-API + TypeScript CLI tooling.
@@ -46,6 +46,13 @@ Flat `{ "abc12345": "message" }` is also accepted.
46
46
 
47
47
  Hash prefixes must be **unique** within the rewrite range.
48
48
 
49
+ ### Tags are never moved
50
+
51
+ `commit apply` does not retarget tags. When a tag points inside the rewritten range, the command prints a warning
52
+ listing every such tag, and the tag keeps pointing at the pre-rewrite commit. Re-create or manually review those tags
53
+ before drafting release notes — otherwise `nifty change-logs` may miss rewritten commits. There is no implicit tag
54
+ migration and no `tag retarget` command today.
55
+
49
56
  ## Retime
50
57
 
51
58
  Spread author and committer timestamps across a window. Writes a **new branch** (default `time-travel`); current branch
@@ -80,5 +87,6 @@ commit apply/retime use gix object writes.
80
87
  | `--dry-run` before `commit apply` | Force-push without user consent |
81
88
  | Explicit `--ref` when HEAD is detached | Use `git rebase -i` when user asked for Nifty tools |
82
89
  | Explain parent relink-only rows in dry-run | Amend commits with `git commit --amend` for bulk history fixes |
90
+ | Re-point affected tags manually after apply | Assume tags follow rewritten commits |
83
91
 
84
92
  After apply, the user must force-update the target ref if it was already published.
@@ -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
@@ -119,7 +125,7 @@ Platform `.node` binaries are **not** uploaded here — the release workflow sta
119
125
  ## CI native staging (maintainers)
120
126
 
121
127
  ```bash
122
- nifty install-native --from-artifacts path/to/native-artifacts
128
+ nifty install-native --from path/to/native-artifacts
123
129
  ```
124
130
 
125
131
  Then `nifty publish` includes staged `@doki-land/nifty-<platform>` packages.
@@ -133,3 +139,7 @@ Then `nifty publish` includes staged `@doki-land/nifty-<platform>` packages.
133
139
  5. **`nifty trust`** for any **new** package name not yet on the Trusted Publisher list
134
140
  6. `nifty change-logs --version X.Y.Z --write` for reference draft
135
141
  7. `nifty upload --release …` when generic assets need GitHub Release upload
142
+
143
+ If history was rewritten with `nifty commit apply`, tags inside that range still point at the pre-rewrite commits
144
+ (apply warns and never moves them). Re-create those tags before step 6 — `nifty change-logs` derives its range from
145
+ tags and would otherwise miss rewritten commits.