Skip to content

chore: npm release workflow (OIDC + provenance) - #2

Merged
oscargws merged 1 commit into
mainfrom
chore/release-workflow
Jul 13, 2026
Merged

oscargws merged 1 commit into
mainfrom
chore/release-workflow

Conversation

@oscargws

Copy link
Copy Markdown
Contributor

Sets up a proper release cycle so the CLI publishes to npm from CI instead of anyone's laptop.

How it works: you cut a GitHub Release tagged vX.Y.Z, and release.yml runs the checks, builds, and publishes with provenance. Auth is npm Trusted Publishing over OIDC, so there's no NPM_TOKEN sitting in the repo. The workflow also checks the tag matches package.json so we can't ship a mismatched version.

Bumps to 0.1.1 so the next release ships the holdings-crash and balances fixes from #1.

One manual step before the first release works: on npmjs, set @redbark/cli's trusted publisher to this repo + release.yml. Written up in RELEASING.md.

Adds a release workflow that publishes with provenance over npm Trusted
Publishing (OIDC, no stored token), triggered by a GitHub Release. Bumps
to 0.1.1 so the next release ships the nullable-holdings and mixed-account
balances fixes.
@oscargws
oscargws merged commit 59fbbb4 into main Jul 13, 2026
1 check passed
@oscargws
oscargws deleted the chore/release-workflow branch July 13, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant