Setup automated publishing to google web extensions store via github actions

[pirate]

[pirate]

@claude can you set this up, tell me what env vars/secrets to set up in settings as well.

It should auto-publish a new version whenever a new release is created on github.

[claude]

Claude finished @pirate's task in 3m 15s —— View job • claude/issue-3-20251212-1956 • Create PR ➔

---

Automated Chrome Web Store publishing setup complete!

I've created a comprehensive setup for automated publishing to the Chrome Web Store. Due to GitHub App permission restrictions, I cannot push workflow files directly, so you'll need to add the workflow file manually.

What I've Added

✅ PUBLISHING.md - Complete documentation including:

• All 4 required secrets with detailed instructions on how to obtain them
• Step-by-step setup guide
• The complete workflow file content
• Troubleshooting tips
• Optional staging process instructions

Required Secrets

You need to configure these 4 secrets in your repository settings (Settings → Secrets and variables → Actions):

1. CHROME_EXTENSION_ID - Your extension's ID from the Chrome Web Store
2. CHROME_CLIENT_ID - OAuth 2.0 Client ID from Google Cloud Console
3. CHROME_CLIENT_SECRET - OAuth 2.0 Client Secret
4. CHROME_REFRESH_TOKEN - OAuth 2.0 Refresh Token for API authentication

See PUBLISHING.md for detailed instructions on obtaining each secret.

Workflow File to Add Manually

Create .github/workflows/publish-chrome-extension.yml with this content:

name: Publish to Chrome Web Store

on:
  release:
    types: [created]

jobs:
  publish:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Setup Bun
        uses: oven-sh/setup-bun@v2
        with:
          bun-version: latest

      - name: Install dependencies
        run: bun install

      - name: Build and pack extension
        run: bun run pack

      - name: Get version from manifest
        id: version
        run: |
          VERSION=$(cat public/manifest.json | grep '"version"' | sed 's/.*"version": "\(.*\)".*/\1/')
          echo "version=$VERSION" >> $GITHUB_OUTPUT

      - name: Publish to Chrome Web Store
        uses: mnao305/chrome-extension-upload@v5.0.0
        with:
          file-path: ./release/improv-ai-userscript-creator-v${{ steps.version.outputs.version }}.zip
          extension-id: ${{ secrets.CHROME_EXTENSION_ID }}
          client-id: ${{ secrets.CHROME_CLIENT_ID }}
          client-secret: ${{ secrets.CHROME_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CHROME_REFRESH_TOKEN }}
          publish: true

How It Works

Once set up, the workflow will:

1. Trigger automatically when you create a new GitHub release
2. Build the extension using bun run pack
3. Extract the version from public/manifest.json
4. Upload and publish to the Chrome Web Store immediately

Next Steps

1. Merge this PR to get the documentation
2. Add the workflow file manually to .github/workflows/publish-chrome-extension.yml
3. Configure the 4 required secrets in repository settings
4. Create a GitHub release to test the automated publishing!

---

Branch: claude/issue-3-20251212-1956 |

[pirate]

I dont see a way to get CHROME_CLIENT_SECRET, the UI only shows a client id and no secret.

Can we do this with an api key instead?

[pirate]

ugh I hate google cloud console so much