[Zanzavar]

Publishing a GitHub release currently leaves publishing @arcweave/arcscript to npm as a separate manual step. Add a release workflow that checks out the release tag, generates the parsers, installs the locked dependencies, builds, tests, and publishes through npm trusted publishing with provenance.

The release tag must match TypeScript/package.json, with an optional v prefix. Stable versions publish to latest; prerelease versions publish to next. GitHub prereleases require a prerelease package version.

Validated locally with parser generation, a frozen pnpm install, the TypeScript build, all 238 tests, actionlint, seven release-validation scenarios, an npm package dry run, and an import of the compiled package. Live npm publishing has not been exercised: npm authorization needs to be configured, and version 3.1.0 is already published.

Before the next release, merge this workflow and add a GitHub Actions trusted publisher in the npm package settings for arcweave/arcscript-interpreters, workflow filename npm-publish.yml, no environment, with direct npm publish allowed. No npm token secret is required.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@arcweave/arcscript@23

commit: 09c7a49