Add CI/CD for Chrome extension

[DIodide]

Summary

• CI workflow (extension-ci.yml): Runs npm ci + npm run build on every PR and push to main that touches extension/. Uploads the build as an artifact for easy testing.
• CD workflow (extension-publish.yml): Automatically uploads and publishes to the Chrome Web Store when a GitHub release is created with an ext-v* tag (e.g. ext-v1.5.0). Can also be triggered manually via workflow_dispatch.

Setup required

Add these 4 secrets to the repo (Settings > Secrets > Actions):

Secret	Description
CHROME_EXTENSION_ID	The extension ID (iejdjhiphonjpgaobmpniifeipiomgee)
CHROME_CLIENT_ID	OAuth 2.0 client ID from Google Cloud Console
CHROME_CLIENT_SECRET	OAuth 2.0 client secret
CHROME_REFRESH_TOKEN	Refresh token obtained via the OAuth flow for the Chrome Web Store API

To get the OAuth credentials, follow the Chrome Web Store API guide.

Release workflow

1. Bump the version in extension/public/manifest.json
2. Merge to main
3. Create a GitHub release with tag ext-v<version> (e.g. ext-v1.5.0)
4. The workflow automatically builds, uploads, and publishes to the Chrome Web Store

Test plan

• Verify CI workflow triggers on PRs touching extension/
• Verify build artifact is uploaded successfully
• Configure Chrome Web Store API secrets
• Test publish workflow via workflow_dispatch
• Test end-to-end with a release tag

🤖 Generated with Claude Code