dsh-loci 2.0.0 → 2.0.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 +32 -0
- package/client.js +1367 -1367
- package/docs/ACCEPTANCE.md +279 -279
- package/docs/PRIVACY.md +93 -93
- package/package.json +2 -2
- package/src/host/index.js +290 -290
- package/src/host/store/audit.js +208 -208
- package/src/host/store/store.js +1538 -1538
- package/src/mcp/store-facade.js +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,38 @@ All notable changes to this project are documented here. The format follows
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the project follows
|
|
5
5
|
[Semantic Versioning](https://semver.org/spec/v2.0.0.html) from 1.0.0.
|
|
6
6
|
|
|
7
|
+
## [2.0.2] — 2026-11-14
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- The manifest gate now checks the `bin` entry: bare relative path, target exists,
|
|
12
|
+
shebang present, covered by `files`. No user-visible behaviour changed — measured
|
|
13
|
+
on the published builds, `bin` was already correct in both 2.0.0 and 2.0.1
|
|
14
|
+
(`node_modules/.bin/dsh-loci` is created and `npx dsh-loci help` works).
|
|
15
|
+
|
|
16
|
+
The reason for the guard: npm rewrites a bin path that starts with `./` and prints
|
|
17
|
+
`script name … was invalid and removed`, which reads like the binary was dropped.
|
|
18
|
+
It was not. The value is now canonical so that warning cannot hide a real problem
|
|
19
|
+
next time.
|
|
20
|
+
|
|
21
|
+
## [2.0.1] — 2026-11-14
|
|
22
|
+
|
|
23
|
+
### Changed
|
|
24
|
+
|
|
25
|
+
- **Publishing now uses Trusted Publishing (OIDC) only.** `setup-node` no longer
|
|
26
|
+
receives `registry-url` and the publish step no longer reads `NODE_AUTH_TOKEN`:
|
|
27
|
+
the collaboration center's npm runbook records both as `ENEEDAUTH` traps, and
|
|
28
|
+
with a Trusted Publisher bound, the OIDC identity token is the credential. The
|
|
29
|
+
repository therefore holds no npm secret.
|
|
30
|
+
- `release.yml` gained an `npm >= 11.5` check, because npm 10 never performs the
|
|
31
|
+
OIDC exchange.
|
|
32
|
+
|
|
33
|
+
### Note
|
|
34
|
+
|
|
35
|
+
`2.0.0` was the bootstrap publish (npm does not allow a first publish over OIDC,
|
|
36
|
+
[npm/cli#8544](https://github.com/npm/cli/issues/8544)), so it carries no
|
|
37
|
+
attestation. **2.0.1 is the first version with a provenance attestation.**
|
|
38
|
+
|
|
7
39
|
## [2.0.0] — 2026-11-14
|
|
8
40
|
|
|
9
41
|
### Added
|