Fix Pushing Staging Extension To Public#386
Merged
Conversation
Apparently the github action just assumes always public and it doesn't have a way to change the behaviour. Switch to the cli to enable such behaviour. ref CSF-1080
GODrums
approved these changes
Apr 8, 2026
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
2 participants
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.
Apparently the github action just assumes always public and it doesn't have a way to change the behaviour. Switch to the cli to enable such behaviour.
ref CSF-1080
Note
Low Risk
Low risk: only updates a GitHub Actions workflow, but it changes the release mechanism and flags used for Chrome Web Store submission, which could affect staging publish behavior if misconfigured.
Overview
Switches the staging Chrome Web Store publish step from
browser-actions/release-chrome-extension@v0.2.1tochrome-webstore-upload-cli@3invoked vianpx.Credentials are now passed via the CLI’s expected env vars (
EXTENSION_ID,CLIENT_ID,CLIENT_SECRET,REFRESH_TOKEN), and the submission is explicitly targeted to trusted testers using--trusted-testersto avoid unintended public publishing.Reviewed by Cursor Bugbot for commit 2d9e667. Bugbot is set up for automated code reviews on this repo. Configure here.