Package Tag Release Process

Package tag release process

This repository currently has two distinct publication paths.

Guarded onchain release

release.yml runs from a package-scoped tag or manual release tag. It requires the tag at current origin/main, builds and validates, checks the committed DAR backup, uploads and records DevNet before Mainnet, creates missing factory metadata when needed, verifies the npm artifact, and publishes.

Before tagging:

1. Review package/source version changes.
2. Build, test, lint, check upgrade compatibility, generate bindings, and verify the package.
3. Back up the candidate DAR and commit dars/ plus dars/dars.lock.

The workflow performs side effects only after those reviewed inputs pass its gates.

npm-only main path

publish.yml also runs on pushes to main and manual dispatch. It builds and publishes npm artifacts, but does not run DAR deployment or deployment-tag gates. A successful npm workflow is not evidence that a DAR was deployed.

Read both workflows and the current scripts before changing version or release policy. Keep secrets in GitHub configuration; public documentation should name required categories without exposing values.