release.yml

name: Release

on:
  push:
    tags: ["v*"]

permissions:
  contents: read
  # Required for npm provenance: the attestation is built from this workflow's
  # OIDC claims, which is what lets npm show where the package was built.
  id-token: write

jobs:
  publish:
    name: publish to npm
    runs-on: ubuntu-latest
    # A GitHub environment, so the token can be scoped to releases and the
    # publish can be gated on a manual approval.
    environment: npm-publish
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: "24"
          registry-url: "https://registry.npmjs.org"
          cache: npm

      - run: npm ci

      # The tag is the only thing a human types during a release. An npm
      # publish cannot be undone, so a mismatch has to fail here.
      - name: Check the tag matches the package version
        run: node scripts/check-release-version.mjs "${{ github.ref_name }}"

      - name: Typecheck
        run: npm run typecheck

      - name: Test
        run: npm test

      # The same check CI runs, reused as the release gate: it packs the
      # tarball, installs it into a clean directory and runs the README
      # example against it. Publishing something that fails this would be
      # publishing something that does not work.
      - name: Verify packaged install and README example
        run: npm run verify:packaged

      - name: Publish
        run: npm publish --provenance --access public --workspace @masterplaycoding/eventlab
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}