Skip to content

Fix Chrome extension release recovery and API upload - #1908

Open
Juice10 wants to merge 8 commits into
mainfrom
codex/chrome-extension-manual-release
Open

Fix Chrome extension release recovery and API upload#1908
Juice10 wants to merge 8 commits into
mainfrom
codex/chrome-extension-manual-release

Conversation

@Juice10

@Juice10 Juice10 commented Jul 22, 2026

Copy link
Copy Markdown
Member

Summary

  • migrate Chrome Web Store publishing from the deprecated API v1 action to pinned chrome-webstore-upload-cli@4.0.1 using API v2
  • preserve automatic stable and next extension publishing after successful npm releases
  • document dashboard-based manual recovery without broadening the privileged npm release workflow
  • correct stale master references in the release-channel documentation

Required repository setup

Production publishing uses CWS_PUBLISHER_ID; the next channel uses NEXT_CWS_PUBLISHER_ID alongside its existing NEXT_CWS_* credentials.

Validation

  • focused workflow and documentation assertions pass
  • workflow YAML, Prettier, actionlint, and git diff --check pass
  • the extension prepublish build succeeds
  • chrome.zip passes integrity validation and contains Manifest V3 version 2.1.1

The 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.

@Juice10
Juice10 marked this pull request as ready for review July 22, 2026 10:32
Copilot AI review requested due to automatic review settings July 22, 2026 10:32

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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_dispatch boolean 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.

Comment thread .github/workflows/release.yml Outdated
@changeset-bot

changeset-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 766ca3c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Juice10 Juice10 changed the title Add manual Chrome extension release trigger Fix Chrome extension release recovery and API upload Jul 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Bundle Size Changes

No bundle size changes.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment thread .github/workflows/release.yml Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comment thread docs/releases/next-channel.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants