ci: auto-publish importable Chrome/Firefox packages to a rolling "latest" release - #4
Merged
Merged
Conversation
…merge to main Add a `publish` job to the CI workflow that, after the existing checks pass on a push to main, zips the Chrome (MV3) and Firefox (MV2) builds and attaches them to a single rolling `latest` pre-release. The tag is re-pointed at the built commit on each run so the release always carries the freshest importable extension packages. - Gated on the `check` job succeeding (typecheck, tests, both builds) - Runs only on push to main, never on pull requests - Scoped `contents: write` only on the publish job - Excludes the Firefox AMO sources zip (not an installable artifact) Co-Authored-By: Claude Opus 4.8 <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.
What
Adds a
publishjob to the CI workflow so that every merge tomainproduces ready-to-import extension packages, attached to a single rollinglatestGitHub pre-release. Users always have a stable URL for the freshest build:…/releases/latest.How it works
After the existing
checkjob (typecheck → unit tests → both browser builds) succeeds on a push tomain, the new job:wxt zipfor Chrome (MV3) andwxt zip -b firefox(MV2).latestpre-release, re-pointing thelatesttag at the exact commit that was built.glance-*-chrome.zipandglance-*-firefox.zip.Decisions
needs: check— a failing build is never published.if: github.event_name == 'push' && github.ref == 'refs/heads/main', so PRs (incl. forks) never trigger it.contents: read; onlypublishgetscontents: write.glance-*-sources.zip) — it's for store review, not installation.Notes
package.jsonversionis still0.0.0, so zip filenames don't differentiate builds; the release notes include the short commit SHA to disambiguate.release.yml(manual, versioned releases) is left untouched and complements this rolling build.main.🤖 Generated with Claude Code