Release v1.2.0 - #17
Merged
Merged
Conversation
Promote the Unreleased changelog section and bump manifest.json and package.json. Tag v1.2.0 after merge to trigger the release workflow. Co-authored-by: Julius Walton <ShiosOS@users.noreply.github.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
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
Release preparation for v1.2.0 — the first release to ship the packaging fix from #15 (v1.1.0's published archives were missing
checks.js), plus everything else in that PR.manifest.jsonandpackage.jsonto 1.2.0[Unreleased]section to[1.2.0] - 2026-07-14with compare linksAll checks pass on this revision (79 tests, typecheck, lint, format, build), and the locally built 1.2.0 archive was inspected: all 15 manifest-referenced files present, including
checks.jsandpages.js.After merging
Tag the merge commit to trigger the release workflow, which builds and publishes the GitHub Release with the
.zip(Chrome) and.xpi(Firefox) attached:The workflow refuses to release if the tag doesn't match
manifest.json, so a mis-tag fails fast. With #16 merged, the AMO-signing and Chrome Web Store steps will be skipped until their secrets are configured.