Remove CRX packaging from release workflow #3
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.
Chrome 75+ rejects self-signed CRX files with
CRX_REQUIRED_PROOF_MISSING. Only CRX files signed through Google's infrastructure or distributed via Chrome Web Store can be installed.Changes
.github/workflows/release.yml: Removed CRX build step and asset uploadREADME.md: Removed CRX references, clarified ZIP-only installation via developer modeUsers must now extract the ZIP and load unpacked in
chrome://extensions/with developer mode enabled—the only viable distribution method outside the Chrome Web Store.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.