@thespielplatz/tsp-tools-theme 0.3.0 → 0.3.2

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 CHANGED
@@ -8,6 +8,46 @@ Consumers pin a caret range and do not auto-update, so a release only reaches a
8
8
  that service's own spec says so. This package has no users of its own — every entry below is a
9
9
  change to eight apps at once, at the moment each of them chooses to take it.
10
10
 
11
+ ## v0.3.2
12
+
13
+ [compare changes](https://github.com/inf0matics/tsp-tools-theme/compare/v0.3.1...v0.3.2)
14
+
15
+ ### 📖 Documentation
16
+
17
+ - An upgrade guide for the consumers, and 0.3.0 IS an API break ([f5ecb38](https://github.com/inf0matics/tsp-tools-theme/commit/f5ecb38))
18
+ - Drop the upgrade guide — the migrations are reworks, not upgrades ([44e3fb0](https://github.com/inf0matics/tsp-tools-theme/commit/44e3fb0))
19
+
20
+ ### 🏡 Chore
21
+
22
+ - No personal paths in the repo, no addresses in the tarball ([e93e559](https://github.com/inf0matics/tsp-tools-theme/commit/e93e559))
23
+
24
+ ## v0.3.1
25
+
26
+ [compare changes](https://github.com/inf0matics/tsp-tools-theme/compare/v0.3.0...v0.3.1)
27
+
28
+ `0.3.1` exists to prove the automated release path end to end: `npm run bump-version` cuts it,
29
+ a pushed tag publishes it over OIDC with no npm token anywhere. It contains no behaviour change —
30
+ no consumer needs it.
31
+
32
+ Provenance was attempted and abandoned: npm signs provenance only for a **public** source
33
+ repository, and this one is private (`422 … Unsupported GitHub Actions source repository
34
+ visibility: "private"`).
35
+
36
+ ### 🩹 Fixes
37
+
38
+ - **ci:** Give the provenance check 10 minutes, not 200 seconds ([801182d](https://github.com/inf0matics/tsp-tools-theme/commit/801182d))
39
+ - **ci:** Drop provenance — it requires a public repository
40
+ - **ci:** Keep package-lock.json in step with the version on release
41
+
42
+ ### 🏡 Chore
43
+
44
+ - Changelogen must not cut the GitHub release ([c564e71](https://github.com/inf0matics/tsp-tools-theme/commit/c564e71))
45
+
46
+ ### 🤖 CI
47
+
48
+ - Ask for provenance explicitly, and verify it landed ([e96945a](https://github.com/inf0matics/tsp-tools-theme/commit/e96945a))
49
+
50
+
11
51
  ## v0.3.0 — 2026-09-22
12
52
 
13
53
  [compare changes](https://github.com/inf0matics/tsp-tools-theme/compare/v0.2.1...main)
package/README.md CHANGED
@@ -358,7 +358,15 @@ rotate and none to leak. Two consequences worth knowing:
358
358
  and would silently look for a token that does not exist; trusted publishing needs npm ≥ 11.5.1
359
359
  and Node ≥ 22.14.0, and the step fails loudly rather than falling back.
360
360
 
361
- Provenance is automatic under trusted publishing — `--provenance` is not passed, and must not be.
361
+ **There is no provenance, and that is not an oversight.** npm only signs provenance for a
362
+ **public** source repository; this one is private, so npm skips the attestation. Asking for it
363
+ explicitly does not produce one — it fails the publish with a 422 (`Unsupported GitHub Actions
364
+ source repository visibility: "private"`), which is how the first `v0.3.1` attempt died. If this
365
+ repository is ever made public, set `publishConfig.provenance` and restore the workflow step that
366
+ checks the attestation actually landed.
367
+
368
+ Trusted publishing is unaffected and is the substantive win either way: there is no token to
369
+ leak, and the registry records the publisher as GitHub Actions over OIDC rather than a person.
362
370
 
363
371
  **`0.3.0` is a special case: it needs a tag, not a bump.** Its version was already written into
364
372
  `package.json` by hand (`0a5c793`) and its changelog entry is written, so two of changelogen's
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thespielplatz/tsp-tools-theme",
3
- "version": "0.3.0",
3
+ "version": "0.3.2",
4
4
  "description": "tsp.tools design-system theme as a Nuxt layer (Nuxt UI v4 + Tailwind v4): amber-on-anthracite tokens (light + dark), Nunito/Space Grotesk fonts, per-area colour mode, and the shared app shell. Use globally via `extends`, or scoped to a sub-area.",
5
5
  "author": "inf0matics",
6
6
  "license": "MIT",
@@ -55,7 +55,7 @@
55
55
  "typecheck": "nuxi typecheck playground && nuxi typecheck scoped",
56
56
  "test:icons": "npm run build:playground && npm run build:scoped && node scripts/check-icons.mjs",
57
57
  "gate": "npm run lint && npm run docs:api:check && npm run typecheck && npm run test:icons && npm run test:e2e",
58
- "bump-version": "npm run gate && changelogen --release && git push --follow-tags",
58
+ "bump-version": "npm run gate && node scripts/bump-version.mjs && git push --follow-tags",
59
59
  "release": "npm run gate && npm publish",
60
60
  "test:e2e": "playwright test",
61
61
  "test": "npm run test:icons && npm run test:e2e"