Fix Chrome extension release recovery and API upload - #1908
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a manual (workflow_dispatch) recovery path to the release workflow so Chrome extension build/upload steps can be triggered even when the npm publication path didn’t mark a release as “published”.
Changes:
- Adds a
workflow_dispatchboolean input (publish_chrome_extension) to manually trigger Chrome extension publishing. - Extends the existing Chrome extension build/upload
if:conditions to also run when manually requested. - Keeps the existing automatic behavior that runs extension publishing after a successful Changesets npm publish.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Bundle Size ChangesNo bundle size changes. |
Summary
chrome-webstore-upload-cli@4.0.1using API v2nextextension publishing after successful npm releasesmasterreferences in the release-channel documentationRequired repository setup
Production publishing uses
CWS_PUBLISHER_ID; thenextchannel usesNEXT_CWS_PUBLISHER_IDalongside its existingNEXT_CWS_*credentials.Validation
git diff --checkpasschrome.zippasses integrity validation and contains Manifest V3 version2.1.1The full local monorepo baseline has unrelated Puppeteer target-close/time-out failures and a missing generated
rrvideo/build/cli.js; the PR's GitHub checks are the remote integration gate.