chore: add npm publish workflow with trusted publishing and release automation

Author: strausr

.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Code Owners - Only these people can approve pull requests
+# All files in the repository require Code Owner approval
+
+* @strausr

.github/workflows/publish.yml

@@ -0,0 +1,45 @@
+name: Publish Package
+
+on:
+  workflow_dispatch:
+
+permissions:
+  id-token: write  # Required for OIDC
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Verify admin permissions
+        run: |
+          # Check if the actor is a repository admin
+          PERMISSION=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            "https://api.github.com/repos/${{ github.repository }}/collaborators/${{ github.actor }}/permission" \
+            | grep -o '"permission":"[^"]*"' | cut -d'"' -f4)
+          
+          if [ "$PERMISSION" != "admin" ]; then
+            echo "Error: Only repository admins can trigger publishing. Current permission: $PERMISSION"
+            exit 1
+          fi
+          
+          echo "✓ Verified admin permission for ${{ github.actor }}"
+
+      - uses: actions/checkout@v4
+
+      - name: Display version to publish
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          echo "📦 Publishing version: $VERSION"
+          echo "version=$VERSION" >> $GITHUB_ENV
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '18'
+          registry-url: 'https://registry.npmjs.org'
+
+      - run: npm ci
+
+      - run: npm test --if-present
+
+      - run: npm publish

.github/workflows/release-please.yml

@@ -0,0 +1,37 @@
+name: Release Please
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v4
+        id: release
+        with:
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+
+      - uses: actions/checkout@v4
+        if: steps.release.outputs.release_created
+
+      - uses: actions/setup-node@v4
+        if: steps.release.outputs.release_created
+        with:
+          node-version: '18'
+
+      - name: Install dependencies
+        if: steps.release.outputs.release_created
+        run: npm ci
+
+      - name: Run post-release tasks
+        if: steps.release.outputs.release_created
+        run: |
+          echo "Release PR created: ${{ steps.release.outputs.pr }}"

README.md

@@ -66,33 +66,3 @@ This project uses [Conventional Commits](https://www.conventionalcommits.org/) f
 - `perf`: Performance improvements
 - `chore`: Other changes
 
-### Version Management
-
-This project uses [release-please](https://github.com/googleapis/release-please) for automated version management.
-
-```bash
-# Install dependencies (includes husky setup)
-npm install
-
-# Update release-please manifest (analyzes commits and updates manifest)
-npm run release
-
-# Create release PR (creates PR with version bump and changelog)
-npm run release:pr
-```
-
-**How it works:**
-1. Make commits with conventional format (`feat:`, `fix:`, etc.)
-2. Run `npm run release` to update the manifest based on commits
-3. Run `npm run release:pr` to create a release PR
-4. Merge the PR to create the release tag
-
-**Version bumps are automatic based on commit types:**
-- `feat:` → minor version (1.0.0 → 1.1.0)
-- `fix:` → patch version (1.0.0 → 1.0.1)
-- `BREAKING CHANGE:` or `feat!:` → major version (1.0.0 → 2.0.0)
-
-**Note:** 
-- Update the `repo-url` in `package.json` scripts with your actual GitHub repo
-- For beta releases, you can manually edit the version in the manifest or PR
-- Alternatively, use `npm version` commands for manual versioning