ci: surface the Chrome Web Store's reason when publish fails - #38
Merged
Merged
Conversation
mnao305/chrome-extension-upload swallowed the response body, so the v0.5.0 release failed with a bare "HTTPError: 400" on publish. The cause (new tabGroups permission without a justification) had to be guessed. Upload and publish now go straight to the v1.1 API with curl: the full response is logged, and the store's message becomes the error annotation. RELEASING.md documents the manual recovery for a failed publish. Co-Authored-By: Claude Opus 5.5 <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.
Why
The v0.5.0 release (run) uploaded fine but failed on publish with only
HTTPError: Response code 400 (Bad Request).mnao305/chrome-extension-uploaddrops the response body. The real cause was the newtabGroupspermission missing a justification, and it had to be guessed.What
curlstep against the same v1.1 API (upload → publish). No new secrets needed.error.message,itemError[].error_detailorstatusDetail[]) becomes the::error::annotation.statuscontainsOK. Codes likeITEM_PENDING_REVIEWnow fail loudly with their explanation.docs/RELEASING.md: how to recover from a failed publish (fix it in the dashboard and submit there; a re-run skips because the draft version already matches).Testing
actionlintpasses.🤖 Generated with Claude Code