publish-package-registry

Automate npm publishing with OIDC provenance by enforcing build gates, semver compliance, and file allowlists to trigger secure, cryptographically verifiable releases without long-lived CI credentials.

OIDC-based trusted publishing is a secure release mechanism that eliminates long-lived secrets by generating cryptographically verifiable artifacts during automated library publication to registries like npm, PyPI, and crates.io.

Yes, the automated release workflow supports dual-module ESM and CJS packages by verifying proper type definitions and module configurations during the pre-publish validation phase to prevent common installation failures.

Eliminate long-lived CI credentials for package registry releases by enforcing strict pre-publish gates and automating releases via secure OIDC-based CI workflows that generate verifiable provenance artifacts.

Automated package publishing fails during pre-publish validation when the strict release gates detect uncommitted git status, build integrity issues, type-checking errors, or files violating the strict allowlist.

Yes, you can use this secure publishing workflow for PyPI and crates.io, as it automates secure library publication across multiple registries using OIDC-based trusted publishing and semver compliance.