1.12.0 (25123)#24
Merged
MStankiewiczOfficial merged 6 commits intomainfrom Dec 20, 2025
Merged
Conversation
The release workflow now only triggers on changes within the src directory. The README has been updated to clarify Chromium installation methods, add a Chrome Web Store installation option, and provide information about the auto-redirect feature.
Replaced the Chrome Web Store badge image URL with the latest official branding in the installation instructions.
Refactored the release workflow to build unsigned artifacts and persist release metadata for follow-up workflows. Added separate workflows to automate publishing signed extensions to Mozilla Add-ons (AMO) and Chrome Web Store (CWS), including uploading signed artifacts to GitHub Releases. This modular approach improves maintainability and separates build from publish steps.
Migrates all browser-specific source files from src/Gecko and src/Chromium into a unified src/browser directory. Adds scripts/build.js to automate building and packaging for Chromium and Gecko targets. Updates GitHub workflows and documentation to use the new build process and directory structure. Cleans up .gitignore for new output paths.
- Added support for localization with `default_locale` set to `en`. - Introduced new `iframeBehavior` option for managing iframe behavior. - Added iframe placeholder. - Updated manifests to include new resources and support localization. - Refactored `translate.js` for improved language handling. - Enhanced error handling and translation in `popup.js`. - Removed the deprecated iframe button functionality.
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.
This pull request introduces a major overhaul of the build and release workflow for the browser extension, automating the packaging and publishing process for both Firefox (AMO) and Chrome (CWS). It adds a new unified build script, splits the release workflow into multiple jobs, and updates documentation to reflect the new process. The changes improve maintainability, automate signing and publishing, and clarify installation and build instructions for users and contributors.
Build and Release Automation
scripts/build.jsNode.js script to automate building browser-specific bundles, flatten and generate locale files, and package unsigned artifacts for both Chromium and Gecko browsers. The script supports CLI flags for browser selection and skipping archive creation..github/workflows/release.ymlto only build and upload unsigned artifacts and release metadata, delegating signing and publishing to follow-up workflows.Publishing Workflows
.github/workflows/publish-amo.ymlto automate signing and uploading the Firefox (Gecko) extension to Mozilla Add-ons, including downloading release metadata, building, signing with web-ext, and updating the GitHub release with the signed XPI..github/workflows/publish-cws.ymlto automate publishing to the Chrome Web Store, including uploading the unsigned bundle, triggering publishing, fetching the signed CRX, and updating the GitHub release.Documentation Updates
README.mdto explain the new build process, clarify installation methods for both browsers (including direct store links), and document the use ofscripts/build.jsfor local builds. Added instructions for enabling auto-redirect and clarified manual installation steps. [1] [2] [3]release-notes.mdto reflect the new version and changes in artifact distribution, including notes about signed/unsigned artifacts and store availability.TRANSLATION-STANDARDS.md, specifying removal criteria for incomplete translations and the process for reintroduction.Other
TRANSLATION-STANDARDS.md.