@ai-matrx/tap-target 0.2.1 → 0.2.3
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/CHANGELOG.md +40 -0
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,45 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.3 — 2026-09-10
|
|
4
|
+
|
|
5
|
+
**The pin is gone for good — this is the release 0.2.2 tried to be.** 0.2.2
|
|
6
|
+
republished to re-point `@ai-matrx/design-system` forward, and then published
|
|
7
|
+
`"0.14.0"` for exactly the same reason 0.2.1 published `"0.11.2"`: `pnpm pack`
|
|
8
|
+
rewrites a `workspace:*` sibling spec to the sibling's EXACT version in the
|
|
9
|
+
packed manifest, so every republish just moved the pin. Chasing it one release
|
|
10
|
+
at a time was never going to end.
|
|
11
|
+
|
|
12
|
+
The class is closed at the mechanism (C15 / C27, THE TRANSITIVE PIN HAZARD):
|
|
13
|
+
the published manifest now declares every `@ai-matrx/*` sibling as `"latest"`,
|
|
14
|
+
while `workspace:*` stays in source for monorepo dev resolution. One shared
|
|
15
|
+
pack step (`apps/shared/scripts/pack-latest-siblings.mjs`) performs the
|
|
16
|
+
rewrite, every package's tarball canary fails on any packed `@ai-matrx/*` spec
|
|
17
|
+
that is not exactly `"latest"`, and `check_ts_sibling_graph.mjs` refuses a
|
|
18
|
+
publish path that stops running either. No source change.
|
|
19
|
+
|
|
20
|
+
### Consumer action
|
|
21
|
+
|
|
22
|
+
none — sibling specs now float.
|
|
23
|
+
|
|
24
|
+
## 0.2.2 — 2026-09-10
|
|
25
|
+
|
|
26
|
+
**A republish so consumers run ONE design-system, not two.** No source change.
|
|
27
|
+
This package's `@ai-matrx/design-system` dependency is `workspace:*`, which the
|
|
28
|
+
publish freezes to whatever the workspace held that day — 0.11.2, on 0.2.1's
|
|
29
|
+
release day. Every consumer that installed both therefore carried two copies of
|
|
30
|
+
the design system in one install graph (`check:matrx-packages`: "ONE SYSTEM,
|
|
31
|
+
ONE VERSION"), and no command a consumer repo can run moves a version a
|
|
32
|
+
published sibling pins. Two copies of a React component package means two sets
|
|
33
|
+
of contexts and two stylesheets, which is the duplicate-package class that has
|
|
34
|
+
already bitten the Vite studio.
|
|
35
|
+
|
|
36
|
+
Cut alongside `@ai-matrx/design-system` 0.14.0 so the spec resolves forward to
|
|
37
|
+
it.
|
|
38
|
+
|
|
39
|
+
### Consumer action
|
|
40
|
+
|
|
41
|
+
`pnpm update -r "@ai-matrx/*" --latest`, then `pnpm check:matrx-packages`.
|
|
42
|
+
|
|
3
43
|
## 0.2.1 — 2026-09-07
|
|
4
44
|
|
|
5
45
|
**Census row 19i is now fully closed — the spinner stops being a coin flip.**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ai-matrx/tap-target",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.3",
|
|
4
4
|
"description": "The AI Matrx tap-target button system: an invisible 44x44 touch ring over a 32x32 visible pill, glass/transparent/solid/group variants with correct ref forwarding for Radix asChild triggers, inline labels, link/label/button trigger resolution with an injectable link component, tooltip wiring, and ~60 pre-composed one-tag buttons.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.cjs",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
},
|
|
58
58
|
"dependencies": {
|
|
59
59
|
"@radix-ui/react-tooltip": "^1.2.8",
|
|
60
|
-
"@ai-matrx/design-system": "
|
|
60
|
+
"@ai-matrx/design-system": "latest"
|
|
61
61
|
},
|
|
62
62
|
"peerDependencies": {
|
|
63
63
|
"react": ">=18.0.0"
|
|
@@ -94,4 +94,4 @@
|
|
|
94
94
|
"test:watch": "vitest",
|
|
95
95
|
"verify:tarball": "node ./scripts/verify-tarball.mjs"
|
|
96
96
|
}
|
|
97
|
-
}
|
|
97
|
+
}
|