Strip manifest key field from the Edge Add-ons package#107
Merged
Conversation
Edge package validation rejects manifests containing "key" (PackageValidationError: "The manifest shouldn't contain the key field"). The key is only needed to pin the Chrome extension id, so the Edge upload now uses a separate zip with the field removed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GitHub deprecated Node 20 action runtimes (forced to Node 24 from 2026-06-16). Bump checkout v4->v6, setup-node v4->v6, upload-artifact v4->v7. 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 first automated Edge publish failed package validation:
The manifest shouldn't contain the key field. Thekeyentry is only needed to pin the Chrome extension id, and Edge rejects packages that include it.The Package step now builds a second zip (
tabox-edge.zip) whose manifest haskeyremoved viajq 'del(.key)', and the Edge upload uses it. The Chrome zip is unchanged.For reference, the Chrome publish step in the same runs failed only because 4.1.2 is already live (
PKG_INVALID_VERSION_NUMBER) — that resolves with the next version bump.🤖 Generated with Claude Code