release.yml

name: Release

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

permissions:
  contents: write
  id-token: write

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: actions/setup-node@v5
        with:
          node-version: 22
          registry-url: https://registry.npmjs.org
      - run: npm ci

      # The tag is the source of truth: publishing a tag that disagrees with
      # package.json is how a version ends up on npm under the wrong number.
      - name: Check the tag matches the package version
        run: |
          tag="${GITHUB_REF_NAME#v}"
          version="$(node -p 'require("./package.json").version')"
          test "$tag" = "$version" || {
            echo "tag $tag does not match package version $version"
            exit 1
          }

      - run: npm run typecheck
      - run: npm run build
      - run: npm run docs:build
      - run: npm run docs:check

      - run: npx playwright install --with-deps
      - run: npm test

      # Re-running a release, or tagging a version published by hand, should not
      # fail the run — only an unpublished version is published here.
      - name: Publish, unless this version is already on the registry
        run: |
          version="$(node -p 'require("./package.json").version')"
          if npm view "partialkit@$version" version > /dev/null 2>&1; then
            echo "partialkit@$version is already on the registry; skipping the publish"
            exit 0
          fi
          npm publish --provenance --access public
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

      - name: Draft the GitHub release
        run: |
          gh release view "$GITHUB_REF_NAME" > /dev/null 2>&1 && exit 0
          gh release create "$GITHUB_REF_NAME" --title "$GITHUB_REF_NAME" --notes-from-tag --verify-tag
        env:
          GH_TOKEN: ${{ github.token }}