Repository navigation
ci: auto-publish to Chrome Web Store on version bump - #100
Merged
Merged
Conversation
Pushes to main that change the package.json version zip the extension and submit it with wxt submit on CWS API v2 (service account). API v1.1 OAuth shuts down 2026-10-15. Merges without a bump skip the job, since the store rejects re-uploads of an existing version.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2039d50. Configure here.
| { | ||
| "name": "alfred", | ||
| "version": "2026.09.26", | ||
| "version": "2026.09.28", |
There was a problem hiding this comment.
Version bump will publish incomplete release
High Severity
This PR bumps package.json and wxt.config.ts to 2026.09.28 without a changelog.json entry. The new publish job submits on any package.json version change, so merging uploads this build to the Chrome Web Store and the in-app changelog still shows 2026.09.26.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 2039d50. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a
publishjob to.github/workflows/ci.ymlthat submits the extension to the Chrome Web Store when a push tomainchanges thepackage.jsonversion.lint-and-buildpasses, onpushonly, so fork PRs never see the secrets.github.event.beforewithHEAD. Merges without a version bump skip the job, since the store rejects a version it already has.wxt zipand uploads withwxt submiton CWS API v2 (service account). API v1.1, which the local.env.submitOAuth refresh token uses, shuts down on 2026-10-15.CHROME_CANCEL_PENDING: true: a new bump cancels any review still in progress, so the newest version is the one under review. Remove it to fail the job instead.concurrency: chrome-web-storekeeps two publish runs from racing.AGENTS.mddocuments the job.Required repo secrets:
CHROME_EXTENSION_ID,CHROME_PUBLISHER_ID,CHROME_SERVICE_ACCOUNT_CLIENT_EMAIL,CHROME_SERVICE_ACCOUNT_PRIVATE_KEY(with real newlines, e.g.jq -r .private_key key.json | gh secret set CHROME_SERVICE_ACCOUNT_PRIVATE_KEY).How to test
.env.submit:bunx wxt zip && bunx wxt submit status --chrome-zip .output/*-chrome.zip. This reads the item status and uploads nothing.publishjob runs and skips, since there's no version bump.Checklist
bun run lintpassesbun run format:checkpasses