Repository navigation
feat(clipper): publish browser extension releases for auto-updates - #294
Merged
Merged
Conversation
Self-hosted builds with update_url (Firefox updates.json, Chrome/Edge update XML and signed CRX), plus Chrome Web Store and Edge Add-ons upload, each only when its secrets exist. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018uA6PhZXrmpgsbfDh2W23u
This was referenced Oct 10, 2026
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
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.
Requested by Adeel · project thread
Description
Before: a release attached the clipper zips, but nothing ever updated an installed clipper.
After: each release also publishes the clipper so installed copies update themselves. Every part runs only when its repository secrets exist and is skipped otherwise:
CWS_EXTENSION_ID,CWS_CLIENT_ID,CWS_CLIENT_SECRET,CWS_REFRESH_TOKEN).EDGE_PRODUCT_ID,EDGE_CLIENT_ID,EDGE_API_KEY).lens-clipper-<browser>.crx, plus the-updates.xmlit polls onreleases/latest/download(CRX_PRIVATE_KEY).lens-clipper-firefox-updates.jsonfor the Mozilla-signed XPI that the Firefox workflow attaches (AMO keys).How: with
EXT_UPDATE_BASEset,build.mjsalso writesdist/<target>-selfhostedwith anupdate_url. For Gecko targets it'sbrowser_specific_settings.gecko.update_url, and Safari is skipped.scripts/release.mjsderives the Chromium extension ID from the key and writes both kinds of update manifest. I checked the ID it derives against Chromium's own for the same key, and checked that headless Chromium packs the.crx. Docs: "Releases and updates" indocs/web-clipper.md.Motivation and Context
Adeel asked for a release pipeline and auto-updates for the browser extensions. Safari updates through the App Store, which the Safari thread handles (#283).
Types of changes
Checklist:
docs/accordingly.Done questions
🤖 Generated with Claude Code
https://claude.ai/code/session_018uA6PhZXrmpgsbfDh2W23u
Generated by Claude Code