Skip to content

RELEASE.md

Latest commit

 

History

History
29 lines (25 loc) · 1.29 KB

RELEASE.md

File metadata and controls

29 lines (25 loc) · 1.29 KB
Raw

Release

Releases are published to npm from GitHub Actions using trusted publishing (OIDC), so no npm token is stored in the repository. Packages get provenance attestations automatically.

  1. Bump the version: 
    npm version <patch|minor|major> --no-git-tag-version
  2. Commit and push to master.
  3. Create a GitHub release with a new tag X.Y.Z (no v prefix, matching earlier releases).
  4. The publish workflow waits for approval in the npm environment, then builds the package and runs npm publish.

One-time setup

  • npm: on npmjs.com → codejar → Settings → Trusted Publisher, add a GitHub Actions publisher with repository antonmedv/codejar, workflow publish.yaml and environment npm. Then set publishing access to "Require two-factor authentication and disallow tokens".
  • GitHub: environment npm (Settings → Environments) with a required reviewer, limited to tags matching *.*.*.
  • GitHub Pages: Settings → Pages → Source: "GitHub Actions". The pages workflow deploys the demo on every push to master.