build(release): strip the manifest key from the store zip - #60
Merged
Conversation
The Chrome Web Store upload rejects manifests containing "key" ("key field
is not allowed in manifest") — it is a local-dev mechanism for pinning the
extension ID. The repo manifest keeps it so unpacked dev installs stay on
the stable ID; the store artifact drops it (the store assigns the real ID
at first upload; update the backend ALLOWED_ORIGINS to that ID before
publishing).
Co-Authored-By: Claude Fable 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.
Summary
The CWS dashboard rejected
optia-1.0.0.zipwith "key field is not allowed in manifest." Thekeyis a local-dev pin for the extension ID; the store won't accept it in uploads. Both zip-building workflows (the release-please attach job and the manual fallback) now deletekeyfromdist/manifest.jsonbefore zipping. The repo manifest keeps it so unpacked dev installs keep the stable ID.Follow-up required at publish time: the store assigns the real extension ID at first upload — once the dashboard shows it, add
chrome-extension://<store-id>toALLOWED_ORIGINSin optia-backend's production vars (keeping the dev ID too) and redeploy before the listing goes live, or the extension's backend calls will be CORS-blocked.A hand-patched
optia-1.0.0-store.zip(identical contents, key stripped) was produced for today's submission, so this PR only needs to land before the next release.🤖 Generated with Claude Code