ci: Bump slsa-builder pin for npm provenance compatibility projection
Summary
- Bumps the release pipeline's slsa-builder reusable workflow pin in
.github/workflows/publish.ymlfrome7c55d9192e4493eb21d40d2b4dbf0bdfb1cbfc2to18611e2d610266fbf9ce2dfd8c382b49ed46a0b5— seven commits ahead on slsa-builder main, headlined by windlasstech/slsa-builder#151 (feat(npm)!: the final npm provenance contract per ADR 0103–0112), plus #147 (dogfood records), #148 (E422 rejection classification under the reduced read-back budget), #154 (publish input-validation classification), #153 (docs), and dependency bumps #149/#150. - The ninth v0.1.3 dogfood (run 41666974638) captured npm's complete
E422rejection for the first time: the registry requiresbuildDefinition.externalParameters.workflow.{ref,repository,path},internalParameters.github.{event_name,repository_id,repository_owner_id}, andresolvedDependencies[0]tracking the invocation source, all matching the signing certificate's public GitHub claims (slsa-builder#143). - The new pin implements that compatibility projection from verified OIDC claims while preserving the immutable Windlass builder identity, both SHA-256/SHA-512 subject digests, and the signed distinction between the built source tag (
v0.1.3/ae5bb155) and the dispatch invocation ref. Unlike the previous diagnostic bumps, this one carries the actual fix candidate: the next dispatch determines whether npm accepts the projection or reports a remaining rejection family.
How to test: merge, then re-run the release workflow via workflow_dispatch with release_tag=v0.1.3 (the tag already exists; no publication is visible in the registry).
Related Issues
- Related windlasstech/slsa-builder#30
- Related windlasstech/slsa-builder#143
Change Type
- Bug fix
- Feature
- Refactor
- Documentation
- Test/CI
- Breaking change
- Other:
Changelog
- Category: None
- User-facing note: No user-facing impact. This is a CI-only pin bump of the release pipeline's provenance producer; the published package ships no behavioral change, and the v0.1.3 changelog section is already finalized on the signed tag.
Changelog update:
-
CHANGELOG.md[Unreleased]updated - Not needed because this change is not user-facing
Checklist
General
- PR title follows Conventional Commits format:
type(scope): Summary - This PR does not expose backend/internal implementation details in a public repo.
- No secrets, tokens, keys, or private endpoints are included.
- Changes stay within this repository's intended scope.
CI/Workflow Changes (if applicable)
- All
uses:references are pinned to full 40-character commit SHAs (with# vX.Y.Zcomment) -
step-security/harden-runneris included as the first step in every job - Job-level
permissionsare used instead of top-levelpermissions
Note: the slsa-builder reusable workflow pin keeps the existing # main, pre-release comment (per docs/release.md, until slsa-builder cuts releases); every other uses: reference is untouched by this diff. The pinned revision's own feat(npm)! breaking marker applies to slsa-builder's pre-release buildType contract (not yet publicly frozen) and does not change this caller's workflow inputs or outputs.
Protocol / Compatibility Impact
- No protocol/spec impact
- Protocol/spec updated
- Conformance tests updated
- Breaking change is versioned and migration notes are included
Testing
- Unit tests added/updated
- Integration or conformance tests added/updated
- Tests pass
- Lint and format pass
- Type check passes
- Manual verification performed
Describe test evidence:
- One-line diff: only the pinned SHA in
jobs.publish.useschanges. - Pin target verified as an existing commit on
windlasstech/slsa-buildermain, exactly seven commits ahead of the current pin (#147–#151, #153, #154, plus dependency bumps #149/#150). publish.ymlparses as valid YAML andjobs.publish.usesresolves to the new pinned ref.- Lefthook pre-commit hooks (oxfmt, markdownlint, oxlint) and the DCO commit-msg hook pass on the commit.
- Unit/integration tests are not applicable: no source, test, or manifest change.
Documentation
- README updated
- Spec/docs updated
- Changelog decision completed above
Rollout / Risk
- Risk level: Low
- Rollback plan: Revert the merge commit to restore the previous pin. No state outside git is affected; the release pipeline is not exercised until the v0.1.3 re-dispatch.
Reviewer Checklist
- Scope is clear and minimal
- Security and boundary checks passed
- Tests and docs are sufficient
- Compatibility impact is correctly handled
Summary by cubic
Bumps the release pipeline's slsa-builder reusable workflow pin so npm accepts the generated provenance.
npm currently rejects the pipeline's provenance with E422 because fields in the build definition and resolved dependencies don't match the signing certificate's GitHub claims. The new pin implements the required compatibility projection from verified OIDC claims while preserving the immutable builder identity and subject digests. CI-only change with no user-facing impact.