Skip to content

fix: protect package publication - #172

Merged
BartWaardenburg merged 2 commits into
mainfrom
fix/supply-chain-release-hardening
Oct 14, 2026
Merged

BartWaardenburg merged 2 commits into
mainfrom
fix/supply-chain-release-hardening

Conversation

@BartWaardenburg

Copy link
Copy Markdown
Collaborator

Validate release crates without publication credentials, then publish with a temporary crates.io identity in the release environment. Prepare npm packages separately and publish ordered, checksum-verified tarballs without checkout, application dependencies or lifecycle scripts.

The release helper and workflow policy suites and actionlint pass. Existing native Rust and package validation remains applicable because the final authentication change only touches the workflow.

Coordinate npm and crates.io environment bindings before integration. Keep existing tokens until an actual publication succeeds with the new identity. No package publication was performed.

Base: main at 624d39b67bd71f0114a89b55db199b8b6c8dd6da. Head: cc85c1a15613677462ef7b8e254b8be443c5904f.

Changed files:

  • .github/scripts/publish-crate-if-needed.sh
  • .github/scripts/publish-crate-if-needed.test.mjs
  • .github/scripts/workflow-policy.test.mjs
  • .github/workflows/release.yml

@BartWaardenburg
BartWaardenburg marked this pull request as ready for review October 14, 2026 08:23
@BartWaardenburg
BartWaardenburg merged commit 7d3af2c into main Oct 14, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant