release-and-publish

You can automate npm and GHCR publishing by using a workflow that validates pre-wrapup conditions, bumps versions, pushes tags, and coordinates releases with retry logic. This ensures synchronized state across all targets.

When an npm registry publish fails, the workflow applies retry logic for transient failures. If errors persist, it stops and reports a partial-state outcome, ensuring you know exactly which destinations need intervention.

To prevent duplicate package versions across multiple registries, the publishing process enforces idempotent behavior. This guarantees that retrying a deployment or re-running the workflow will not create duplicate entries in your destinations.

The best way to publish a finalized release to the MCP Registry and npm is to run an automated workflow after git wrap-up. It handles version bumping, changelog updates, and verifies success across all configured destinations.

Updating the changelog before publishing a package version is a pre-wrapup requirement. The workflow validates that the changelog is updated alongside the version bump and git tag to ensure release-ready artifacts before deployment.

Yes, you can publish to GHCR and npm simultaneously within one workflow. The automation coordinates publishing across all targets, applying retry-on-transient-failure logic to manage synchronization and verify each destination.