-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update webext packages #553
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/webext-packages
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
July 7, 2023 10:40
c5846ed
to
667918a
Compare
renovate
bot
changed the title
chore(deps): update dependency @types/webextension-polyfill to v0.10.1
chore(deps): update dependency @types/webextension-polyfill to v0.10.2
Aug 22, 2023
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
August 22, 2023 19:53
667918a
to
0359ee7
Compare
renovate
bot
changed the title
chore(deps): update dependency @types/webextension-polyfill to v0.10.2
chore(deps): update webext packages
Sep 7, 2023
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
September 7, 2023 13:42
0359ee7
to
9c8e3b5
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
3 times, most recently
from
September 28, 2023 14:46
816f041
to
b44d630
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
2 times, most recently
from
October 18, 2023 19:07
8b1e8c3
to
ec40092
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
November 7, 2023 22:30
ec40092
to
fa373dd
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
November 22, 2023 02:05
fa373dd
to
912fd75
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
December 4, 2023 13:52
912fd75
to
77b4e9a
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
January 9, 2024 19:52
77b4e9a
to
77a1d7b
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
January 24, 2024 17:29
77a1d7b
to
fb3d4cc
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
February 29, 2024 15:27
fb3d4cc
to
c2a6535
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
3 times, most recently
from
March 25, 2024 18:10
e8c4b0f
to
fe58215
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
April 16, 2024 16:16
fe58215
to
1cd921f
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
May 14, 2024 18:18
1cd921f
to
0ca38fe
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
May 27, 2024 22:31
0ca38fe
to
544cb94
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
August 13, 2024 10:19
544cb94
to
0d8f12c
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
August 28, 2024 20:16
0d8f12c
to
eb8b9d6
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
3 times, most recently
from
September 12, 2024 00:02
99f29f6
to
545ebd4
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
October 8, 2024 19:59
545ebd4
to
245be46
Compare
renovate
bot
force-pushed
the
renovate/webext-packages
branch
from
December 5, 2024 22:41
245be46
to
4545db9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
0.10.0
->0.12.1
1.20.2
->1.20.3
4.18.2
->4.21.2
7.6.2
->7.12.0
0.10.0
->0.12.0
Release Notes
expressjs/body-parser (body-parser)
v1.20.3
Compare Source
===================
depth
option to customize the depth level in the parserdepth
level for parsing URL-encoded data is now32
(previously wasInfinity
)expressjs/express (express)
v4.21.2
Compare Source
v4.21.1
Compare Source
What's Changed
Full Changelog: expressjs/express@4.21.0...4.21.1
v4.21.0
Compare Source
What's Changed
"back"
magic string in redirects by @blakeembrey in https://github.com/expressjs/express/pull/5935New Contributors
Full Changelog: expressjs/express@4.20.0...4.21.0
v4.20.0
Compare Source
==========
depth
option to customize the depth level in the parserdepth
level for parsing URL-encoded data is now32
(previously wasInfinity
)res.redirect
\
,|
, and^
to align better with URL specoptions.maxAge
andoptions.expires
tores.clearCookie
v4.19.2
Compare Source
==========
v4.19.1
Compare Source
==========
v4.19.0
Compare Source
v4.18.3
Compare Source
==========
mozilla/web-ext (web-ext)
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
mozilla/webextension-polyfill (webextension-polyfill)
v0.12.0
Compare Source
Bug Fixes
See all changes for 0.12.0
v0.11.0
Compare Source
Bug Fixes
See all changes for 0.11.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.