Skip to content

fix(extension): package manifest icons - #40

Merged
swsgbl merged 2 commits into
mainfrom
fix/extension-icon-packaging-20261102
Nov 2, 2026
Merged

swsgbl merged 2 commits into
mainfrom
fix/extension-icon-packaging-20261102

Conversation

@swsgbl

@swsgbl swsgbl commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • copy the three PNG icons referenced by generated extension manifests into every unpacked target
  • extend the build test so every manifest icon path must exist after packaging

Evidence

  • public main 80147e4 CI run 41268803273 failed Chrome/Edge loadUnpacked because icon-48.png was missing
  • isolated validation on this patch: extension/adapters tests 7 pass / 0 fail, full workspace build passed, npm run typecheck passed
  • local port 7789 is occupied by an unrelated long-running bridge, so the local real-browser suite correctly skips; GitHub CI is the acceptance run

Follow-up

  • merge only after the PR CI run is green
  • keep the later Pages GEO repair separate from this packaging fix

@swsgbl
swsgbl merged commit b610115 into main Nov 2, 2026
1 check passed
@swsgbl
swsgbl deleted the fix/extension-icon-packaging-20261102 branch November 2, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant