chore(deps): update webext packages (major) #482
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 PR contains the following updates:
7.6.2
->8.3.0
5.0.5
->6.0.1
Release Notes
mozilla/web-ext (web-ext)
v8.3.0
Compare Source
main changes
addons-linter
to 7.1.0 (#3254)mz
dependency (#3215)node-fetch
dependency (#3217)dependencies
@babel/runtime
to 7.25.6 (#3236)chrome-launcher
to 1.1.2 (#3200)firefox-profile
to 4.7.0 (#3224)https-proxy-agent
to 7.0.5 (#3184)jose
to 5.9.2 (#3253)pino
to 9.4.0 (#3240)update-notifier
to 7.3.1 (#3244)watchpack
to 2.4.2 (#3223)ws
to 8.18.0 (#3187)dev dependencies
@babel/cli
to 7.25.6 (#3237)@babel/core
to 7.25.2 (#3210)@babel/eslint-parser
to 7.25.1 (#3206)@babel/preset-env
to 7.25.4 (#3228)@commitlint/cli
to 19.5.0 (#3249)@commitlint/config-conventional
to 19.5.0 (#3248)babel-plugin-istanbul
to 7.0.0 (#3189)chai
to 4.5.0 (#3204)eslint-plugin-import
to 2.30.0 (#3239)mocha
to 10.7.0 (#3202)prettier
to 3.3.3 (#3196)sinon
to 19.0.2 (#3252)others
See all changes: mozilla/web-ext@8.2.0...8.3.0
v8.2.0
Compare Source
features
addons-linter
v6.30.1bug fixes, etc.
dependencies
jose
to 5.4.1 (#3174)mkdirp
to 3.0.1 (#2735)ws
to 8.17.1 (#3171)See all changes: mozilla/web-ext@8.1.0...8.2.0
v8.1.0
Compare Source
features
addons-linter
v6.29.0bug fixes, etc.
braces
version to fix GHSA-grv7-fg5c-xmjg (#3169)dependencies
@babel/runtime
to 7.24.7 (#3160)jose
to 5.4.0 (#3157)dev dependencies
@babel/cli
to 7.24.7 (#3161)@babel/core
to 7.24.7 (#3162)@babel/eslint-parser
to 7.24.7 (#3158)@babel/preset-env
to 7.24.7 (#3159)chai-as-promised
to 8.0.0 (#3165)nyc
to 17.0.0 (#3166)prettier
to 3.3.2 (#3168)See all changes: mozilla/web-ext@8.0.0...8.1.0
v8.0.0
Compare Source
What's changed
300+ commits have been written to get this new version 8 out of the door (see link to the full changelog at the bottom). Please take a look at the official documentation to know what has changed but expect some breaking changes.
Specifically,
web-ext sign
has been heavily refactored. Among other things, you can create new add-ons (not just versions) from the command line now 🎉 Unfortunately, this command is not backward compatible with v7.While we're keeping the v7 branch around to ease the transition, we will mainly fix bugs and introduce new features in v8.
New contributors
Full changelog: mozilla/web-ext@7.12.0...8.0.0
v7.12.0
Compare Source
📣 We're finalizing web-ext v8 (the next major release), which will use a new AMO API to sign add-ons. Please try it out now by passing the
--use-submission-api
flag to thesign
command in web-ext v7. More information at: https://extensionworkshop.com/documentation/develop/web-ext-command-reference-v7/#use-submission-apifeatures
addons-linter
to6.28.0
See all changes: mozilla/web-ext@7.11.0...7.12.0
v7.11.0
Compare Source
📣 We're finalizing web-ext v8 (the next major release), which will use a new AMO API to sign add-ons. Please try it out now by passing the
--use-submission-api
flag to thesign
command in web-ext v7. More information at: https://extensionworkshop.com/documentation/develop/web-ext-command-reference/#use-submission-apiFeatures
addons-linter
to6.21.0
READ_EXTERNAL_STORAGE
permission requirement (backport #3018)See all changes: mozilla/web-ext@7.10.0...7.11.0
v7.10.0
Compare Source
Features
addons-linter
to6.20.0
fx-runner
to1.4.0
See all changes: mozilla/web-ext@7.9.0...7.10.0
v7.9.0
Compare Source
Features
6.19.0
(it was6.13.0
before)See all changes: mozilla/web-ext@7.8.0...7.9.0
v7.8.0
Compare Source
main changes
Warn web-ext v7 users about upcoming changes to the sign command: as of v8, the
submission API will be used (instead of the signing API) and users will likely
need to take some actions. Users of v7 can already test this upcoming change by
using
web-ext sign --use-submission-api
.v7.7.0
Compare Source
main changes
addons-linter
to 6.13.0 (#2870)eslint
to 8.48.0 (#2853)See all changes: mozilla/web-ext@7.6.2...7.7.0
zikaari/webext-bridge (webext-bridge)
v6.0.1
Compare Source
v6.0.0
Compare Source
This revision is primarily focused on codebase improvements all around. The code should be now much
more readable and easy to comprehend as the responsibilities have been split into smaller pieces and
composed as needed by each runtime context.
For end users of the library, the breaking changes aren't that "breaking", they'll just need to do a
bit of import restructring. The API behaviour is mostly unchanged, with just minor exceptions.
Breaking changes
webext-bridge
. You must import the relevant part yourself depending on the context, eg:import Bridge from 'webext-bridge/window'
for a script that'll be running in the Window context. Learn more about the change here.
setNamespace
is not available in any context exceptwindow
, andallowWindowMessaging
is not available in any context exceptcontent-script
.getCurrentContext
export has been removed.isInternalEndpoint
returnstrue
for some new contexts. In summary it'll betrue
forbackground
,content-script
,devtools
,popup
, andoptions
.background
, message queuing feature can no longer be trusted due to manifest v3 terminating the service worker runtime after certain time. The queue of messagessent from
background
will be disposed off along with the termination of the said service worker. Queuing still works for messages sent from all other contexts.Fixes
content-script
orwindow
when being sent by some other context right after a tab had navigated forward or back. This was caused by old port'sonDisconnect
callback being called after the new port'sonConnect
callback. TheonDisconnect
would then remove the port mapping preventing messages from being routed tocontent-script
orwindow
.that's never coming back. Now, the
sendMessage
call in the sender will reject with an error.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.