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 }}
This repository was archived by the owner on Nov 14, 2025. It is now read-only.
refactor: fail publish workflow if pre-built artifacts are missing (#312)
Previously, the NPM and GitHub Packages publish jobs would fall back to
building from source if the pre-built artifacts from the Main workflow
were not found. This created a risk of publishing untested code.
Changes:
- Removed continue-on-error flag from artifact download steps
- Removed fallback logic that would build from source
- Simplified extraction steps to fail fast with clear error messages
- Renamed "Try to download" to "Download" reflecting mandatory nature
This ensures the publish workflow only succeeds when it can use the
exact artifacts that were built, tested, and scanned in the Main
workflow, maintaining supply chain integrity and build reproducibility.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude <noreply@anthropic.com>
Remove fallback to build from source in publish workflow
6
+
7
+
The NPM and GitHub Packages publish jobs now fail explicitly if pre-built artifacts are not found, instead of falling back to building from source. This ensures we always publish exactly what was tested and validated in the Main workflow, maintaining supply chain integrity.
0 commit comments