You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f1a37b5
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,13 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
14
14
- The release pipeline's slsa-builder provenance producer was updated to a newer pinned revision.
15
15
Release provenance now records the pinned Node.js runtime used by the build, and the publish stage
16
16
uses a pinned, digest-verified npm CLI (11.21.1) that carries the upstream fix for
17
-
[npm/cli#9882](https://github.com/npm/cli/pull/9882): under npm trusted publishing, the CLI
18
-
auto-generated its own provenance and silently discarded the bundle supplied via
19
-
`--provenance-file` (fixed in npm 12.1.0 and 11.20.0). Consequently, the v0.1.3 npm registry
20
-
attestation carries the Windlass-signed SLSA provenance statement, with both SHA-256 and SHA-512
21
-
subject digests and the signed `source.*` build identity, whereas the v0.1.2 registry attestation
22
-
was an npm-generated statement because of that upstream defect
17
+
[npm/cli#9879](https://github.com/npm/cli/issues/9879) (fixed by
18
+
[npm/cli#9882](https://github.com/npm/cli/pull/9882), shipped in npm 12.1.0 and 11.20.0): under
19
+
npm trusted publishing, the CLI auto-generated its own provenance and silently discarded the
20
+
bundle supplied via `--provenance-file`. Consequently, the v0.1.3 npm registry attestation carries
21
+
the Windlass-signed SLSA provenance statement, with both SHA-256 and SHA-512 subject digests and
22
+
the signed `source.*` build identity, whereas the v0.1.2 registry attestation was an npm-generated
23
+
statement because of that upstream defect
23
24
([windlasstech/slsa-builder#97](https://github.com/windlasstech/slsa-builder/issues/97)). The
24
25
builder now also enforces the consumer manifest's package-manager version window before install.
0 commit comments