ci: simplify publish auth flow (#33)

## Summary
- remove PAT-based release mutation from the publish workflow
- align release flow with the simpler ui-style model
- update README release docs to match the actual workflow

## Changes
- remove `workflow_dispatch` bump input
- stop bumping and committing `package.json` inside the release workflow
- remove `secrets.RELEASE_PAT` dependency from checkout
- add a tag-exists guard before release tagging
- keep npm publishing on OIDC with provenance
- document the new flow in `README.md`

## Release model after this PR
- version bump happens in a normal PR to `main`
- canary publishes on pushes to `main`
- release workflow is manually dispatched
- release job reads current package version, tags it, publishes via
OIDC, and creates a GitHub release

## Validation
- `pnpm lint`
- `pnpm typecheck`
- `pnpm build`
- `pnpm test`

Author: bntvllnt

.github/workflows/publish.yml

@@ -7,16 +7,7 @@ on:
       - "src/**"
       - "pnpm-lock.yaml"
       - ".github/workflows/publish.yml"
-  workflow_dispatch:
-    inputs:
-      bump:
-        description: "Version bump type"
-        required: true
-        type: choice
-        options:
-          - patch
-          - minor
-          - major
+  workflow_dispatch: {}
 
 concurrency:
   group: publish-${{ github.event_name }}
@@ -78,19 +69,16 @@ jobs:
       - name: Build
         run: pnpm build
 
-      - name: Upgrade npm for OIDC support
-        run: npm install -g npm@latest
-
       - name: Publish canary
         run: |
           sed -i '/_authToken/d' "$NPM_CONFIG_USERCONFIG"
           unset NODE_AUTH_TOKEN
           BASE_VERSION=$(node -p "require('./package.json').version")
           SHORT_SHA=$(echo "$GITHUB_SHA" | cut -c1-7)
           CANARY_VERSION="${BASE_VERSION}-canary.${SHORT_SHA}"
-          npm version "$CANARY_VERSION" --no-git-tag-version
+          npm version "$CANARY_VERSION" --no-git-tag-version --ignore-scripts
           TARBALL=$(pnpm pack --pack-destination /tmp | tail -1)
-          npm publish "$TARBALL" --tag canary --provenance --access public
+          npx --yes npm@latest publish "$TARBALL" --tag canary --provenance --access public
 
   release:
     name: Publish Release
@@ -104,7 +92,6 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-          token: ${{ secrets.RELEASE_PAT }}
 
       - uses: pnpm/action-setup@v4
 
@@ -119,12 +106,15 @@ jobs:
       - name: Build
         run: pnpm build
 
-      - name: Bump version
+      - name: Read version + guard against retag
         id: version
         run: |
-          npm version ${{ inputs.bump }} --no-git-tag-version
           VERSION=$(node -p "require('./package.json').version")
           echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          if git rev-parse "v${VERSION}" >/dev/null 2>&1; then
+            echo "::error::Tag v${VERSION} already exists. Bump package.json on main via a PR before dispatching release."
+            exit 1
+          fi
 
       - name: Generate changelog
         id: changelog
@@ -163,24 +153,19 @@ jobs:
             echo "CHANGELOG_EOF"
           } >> "$GITHUB_OUTPUT"
 
-      - name: Commit and tag
+      - name: Tag release
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
-          git add package.json
-          git commit -m "chore(release): v${{ steps.version.outputs.version }}"
           git tag -a "v${{ steps.version.outputs.version }}" -m "v${{ steps.version.outputs.version }}"
-          git push origin main --follow-tags
-
-      - name: Upgrade npm for OIDC support
-        run: npm install -g npm@latest
+          git push origin "v${{ steps.version.outputs.version }}"
 
       - name: Publish to npm
         run: |
           sed -i '/_authToken/d' "$NPM_CONFIG_USERCONFIG"
           unset NODE_AUTH_TOKEN
           TARBALL=$(pnpm pack --pack-destination /tmp | tail -1)
-          npm publish "$TARBALL" --tag latest --provenance --access public
+          npx --yes npm@latest publish "$TARBALL" --tag latest --provenance --access public
 
       - name: Create GitHub Release
         env:

README.md

@@ -207,26 +207,31 @@ codebase-intelligence <command> <path>
 
 ## Release
 
-Publishing is automated and **only happens on `v*` tags**.
-
-### One-time setup
-
-1. Create an npm automation token (npmjs.com → Access Tokens).
-2. Add it to GitHub repository secrets as `NPM_TOKEN`.
+Publishing is automated through GitHub Actions.
 
 ### Normal CI (before release)
 
 - `CI` workflow runs on every PR and push to `main`:
   - lint → typecheck → build → test
 
+### Canary publish
+
+- Pushes to `main` trigger a canary publish.
+- The package is published to npm with the `canary` tag.
+- Canary versions are derived from the current package version plus the short commit SHA.
+
 ### Create a release
 
-1. Bump `package.json` version.
-2. Commit: `chore(release): bump to vX.Y.Z`
-3. Tag: `git tag vX.Y.Z`
-4. Push: `git push origin main --tags`
+1. Bump `package.json` version in a normal PR.
+2. Merge that PR to `main`.
+3. Run the `Publish` workflow manually from GitHub Actions.
+4. The workflow will:
+   - verify the tag does not already exist
+   - create and push `vX.Y.Z`
+   - publish to npm with provenance via OIDC
+   - create a GitHub Release with generated notes
 
-The `v*` tag triggers the `CI` workflow publish job (`npm publish --access public --provenance`).
+No PAT is required for npm publish. The workflow uses GitHub repository permissions for tagging and OIDC for npm publishing.
 
 ## Contributing