fix: replace CWS upload action with direct API calls#32
Merged
Conversation
The mnao305/chrome-extension-upload action swallows the Chrome Web Store publish API response body, making it impossible to diagnose why publish returns 400. Replace with direct curl calls that log both the upload and publish responses so the actual error reason is visible in CI logs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
mnao305/chrome-extension-uploadaction swallows the CWS publish API response body — all we see is400 Bad Requestwith no explanationcurlcalls to the CWS API that log both upload and publish responsesrelease.yml(snapshot/testers) andpublish-extension.yml(production)env:variables, never inline inrun:blocksOnce this runs, the publish response will show the actual
statusDetailfrom CWS explaining why publish is rejected (e.g., pending review, policy violation, missing fields).Test plan
workflow_dispatch— the publish step will now show the full CWS error response🤖 Generated with Claude Code