chore(deps): update many non-major #9
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
automerge
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
dd28599
to
d92fd98
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
d92fd98
to
ce46800
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/many-non-major
branch
3 times, most recently
from
de59699
to
c02cc53
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
3 times, most recently
from
a519b18
to
b1b44b4
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
b1b44b4
to
039d8c9
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
039d8c9
to
0f9fada
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
9 times, most recently
from
cb4e002
to
1edb79d
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
abc38f6
to
777093d
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
777093d
to
e7428f1
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
f03ad04
to
362b56b
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
362b56b
to
6d9a46f
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
6d9a46f
to
7160800
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
bb02b17
to
487f3b3
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
91ce230
to
2e7ae71
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
2e7ae71
to
6d14c7c
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
3 times, most recently
from
ca70420
to
7b5b2ba
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
7b5b2ba
to
768d922
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
768d922
to
646a980
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
3 times, most recently
from
e3386a3
to
57609a1
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
57609a1
to
195a354
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
195a354
to
7be5801
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
1f04e8e
to
c426e06
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
30a879d
to
2bd779b
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
2bd779b
to
02e29a0
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
02e29a0
to
3f774db
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
3f774db
to
4f73d23
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
4f73d23
to
7939816
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
2 times, most recently
from
96c9536
to
a70ca6a
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
a70ca6a
to
7148b30
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
7148b30
to
684bd6c
Compare
renovate
bot
force-pushed
the
renovate/many-non-major
branch
from
684bd6c
to
6869ec1
Compare
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.
This PR contains the following updates:
^2.26.14->^2.29.3^9.9.0->^9.12.0^3.14.1->^3.24.1^9.12.1->^9.23.32.1.4->2.2.212->12.22.12Release Notes
BrowserSync/browser-sync (browser-sync)
v2.29.3: The one that fixes snippetOptionsCompare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.29.2...v2.29.3
v2.29.2Compare Source
v2.29.1Compare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.29.0...v2.29.1
v2.29.0: The one that restores IE11 support 💪Compare Source
What's Changed
esbuild does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally broke
IE11support 😢This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers.
So, IE11 will work once again 🎉. Please use the issues thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved)
### IE11 works, again npm install browser-sync@latestFull Changelog: BrowserSync/browser-sync@v2.28.3...v2.29.0
v2.28.3Compare Source
v2.28.2Compare Source
v2.28.1Compare Source
v2.28.0: the one that finally removesdocument.writeCompare Source
What's Changed
Full Changelog: BrowserSync/browser-sync@v2.27.12...v2.28.0
v2.27.12Compare Source
v2.27.11Compare Source
v2.27.10Compare Source
v2.27.9: 2.27.9Compare Source
What's Changed
A bug prevented the help output from displaying - it was introduced when the CLI parser
yargswas updated, and is now fixed :)Full Changelog: BrowserSync/browser-sync@v2.27.8...v2.27.9
v2.27.8: 2.27.8Compare Source
This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)
PR:
Resolved Issues:
Thanks to @lachieh for the original PR, which helped me land this fix
v2.27.7Compare Source
v2.27.6Compare Source
v2.27.5Compare Source
v2.27.4Compare Source
v2.27.3Compare Source
v2.27.1: addedsnippet: booleanoptionCompare Source
This release adds a feature to address https://github.com/BrowserSync/browser-sync/issues/1882
Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new
snippetoption :)browser-sync . --no-snippetor in any Browsersync configuration
the original request was related to Eleventy usage, so here's how that would look
firebase/firebase-admin-node (firebase-admin)
v9.12.0: Firebase Admin Node.js SDK v9.12.0Compare Source
New Features
Bug Fixes
Miscellaneous
v9.11.1: Firebase Admin Node.js SDK v9.11.1Compare Source
Bug Fixes
Miscellaneous
v9.11.0: Firebase Admin Node.js SDK v9.11.0Compare Source
New Features
Miscellaneous
v9.10.0: Firebase Admin Node.js SDK v9.10.0Compare Source
New Features
Bug Fixes
Miscellaneous
firebase/firebase-functions (firebase-functions)
v3.24.1Compare Source
v3.24.0Compare Source
v3.23.0Compare Source
v3.22.0Compare Source
v3.21.2Compare Source
toJSONwas not defined inUserRecord(#1125).v3.21.1Compare Source
v3.21.0Compare Source
[@type](#1088)v3.20.1Compare Source
v3.20.0Compare Source
v3.19.0Compare Source
v3.18.1Compare Source
v3.18.0Compare Source
v3.17.2Compare Source
v3.17.1Compare Source
v3.17.0Compare Source
optionsproperty.v3.16.0Compare Source
v3.15.7Compare Source
v3.15.6Compare Source
v3.15.5Compare Source
v3.15.4Compare Source
v3.15.3Compare Source
v3.15.2Compare Source
firebase emulators:starton older CLIsv3.15.1Compare Source
v3.15.0Compare Source
runWith().toJSONcould not be logged successfully (#907).firebase/firebase-tools (firebase-tools)
v9.23.3Compare Source
v9.23.2Compare Source
firebase init hosting:githubwith no Hosting config infirebase.json. (#3113)remoteconfig:getwas not fetching the latest version by default. (#3559)v9.23.1Compare Source
--projectflag duringinitwould not be recognized with a default project already set. (#3870)v9.23.0Compare Source
firebase deploy --only extensionsnow supports project specifc .env files. When deploying to multiple projects, param values that are different between projects can be put inextensions/${extensionInstanceId}.env.${projectIdOrAlias}and common param values can be put inextensions/${extensionInstanceId}.env.v9.22.0Compare Source
firebase ext:exportcommand, and addsextensionstofirebase deploy. See https://firebase.google.com/docs/extensions/reuse-project-config for more infomation on how to manage your extensions with these commands.initwould crash with multiple Hosting items selected (#3742).crashlytics:symbols:upload) to upload native symbol files, used in Android NDK crash symbolication.v9.21.0Compare Source
v9.20.0Compare Source
ext:install,ext:updateandext:configurenow support param typesecret.v9.19.0Compare Source
ext:dev:publishandext:updatenow support --force and --non-interactive flags.login:usewas not being correctly loaded (#3759).v9.18.0Compare Source
ext:installnow supports--forceand--non-interactiveflags.--no-authorized-domains, skipping syncing with Firebase Auth, when deploying to a Firebase Hosting channel (#3740).functions:list) for listing all functions in the Firebase project.appdistribution:testers:addandappdistribution:testers:removecommands.v9.17.0Compare Source
nodejs16runtime for Cloud Functions.ext:updatenow displays release notes for the versions you are updating to.ext:dev:publishnow checks for a CHANGELOG.md file before publishing.firebase ext:dev:initnow creates a placeholderCHANGELOG.mdfile.--projectflag.firebase init hostingnow supports the version 9 compatibility SDK (#3711).v9.16.6Compare Source
v9.16.5Compare Source
firebase emulator:execthrowing errors when run without project ID. (#3681)v9.16.4Compare Source
v9.16.3Compare Source
v9.16.2Compare Source
v9.16.1Compare Source
--exceptflag when used for deploying Hosting. (#3397)v9.16.0Compare Source
v9.15.1Compare Source
firebase.jsonschema was not packaged in the module. (#3561)v9.15.0Compare Source
ext:dev:emulator:*was not providing the correct parameter values to the emulated extension (#2928)contextin the Functions emulator. (#3536)v9.14.0Compare Source
storage.rulesduringfirebase init(#1833)v9.13.1Compare Source
firebase init hosting:github(#3498)v9.13.0Compare Source
firebase init databasefailure when no project is selected (#2981)firebase init databaseoverwrites entirefirebase.json(#3299)functions:shellerror with background functions (#3490)lots0logs/gh-action-get-changed-files (lots0logs/gh-action-get-changed-files)
v2.2.2: [FIX]: v2.2.2Compare Source
v2.2.1: [MAINTENANCE] v2.2.1Compare Source
v2.2.0: [MAINTENANCE] v2.2.0Compare Source
nodejs/node (node)
v12.22.12: 2022-04-05, Version 12.22.12 'Erbium' (LTS), @richardlauCompare Source
Notable Changes
This is planned to be the final Node.js 12 release. Node.js 12 will
reach End-of-Life status on 30 April 2022, after which it will no
receive updates. You are strongly advised to migrate your applications
to Node.js 16 or 14 (both of which are Long Term Support (LTS) releases)
to continue to receive future security updates beyond 30 April 2022.
This release fixes a shutdown crash in Node-API (formerly N-API) and a
potential stack overflow when using
vm.runInNewContext().The list of GPG keys used to sign releases and instructions on how to
fetch the keys for verifying binaries has been synchronized with the
main branch.
Commits
1193290f3f] - deps: V8: cherry-pickcc9a8a3(devsnek) #42065333eda8d03] - doc: add a note about possible missing lines to readline.asyncIterator (Igor Mikhalev) #34675518a49c0c6] - doc: use openpgp.org for keyserver examples (Nick Schonning) #3922711aef2ad03] - doc: update release key for Danielle Adams (Danielle Adams) #36793a9c38f1003] - doc: add release key for Danielle Adams (Danielle Adams) #35545a35f553889] - doc: add release key for Bryan English (Bryan English) #421025f104e3218] - node-api: cctest on v8impl::Reference (legendecas) #38970e23c04f0dc] - node-api: avoid SecondPassCallback crash (Michael Dawson) #38899a7224c9559] - node-api: fix shutdown crashes (Michael Dawson) #3849281b4dc88f1] - node-api: make reference weak parameter an indirect link to references (Chengzhong Wu) #380002aa9ca1ea9] - node-api: fix crash in finalization (Michael Dawson) #37876a2f4206415] - node-api: stop ref gc during environment teardown (Gabriel Schulhof) #37616171bb66ccc] - node-api: force env shutdown deferring behavior (Gabriel Schulhof) #37303e707514c80] - src: fix finalization crash (James M Snell) #38250v12.22.11: 2022-03-17, Version 12.22.11 'Erbium' (LTS), @richardlauCompare Source
This is a security release.
Notable changes
Update to OpenSSL 1.1.1n, which addresses the following vulnerability:
BN_mod_sqrt()reachable when parsing certificates (High)(CVE-2022-0778)More details are available at https://www.openssl.org/news/secadv/20220315.txt
Fix for building Node.js 12.x with Visual Studio 2019 to allow us to continue to
run CI tests.
Commits
e3e5bf11ba] - build: pin Windows GitHub runner to windows-2019 (Richard Lau) #42349f41e7771bf] - build: fix detection of Visual Studio 2019 (Richard Lau) #42349c372ec207d] - deps: update archs files for OpenSSL-1.1.n (Richard Lau) #42348d574a1dccb] - deps: upgrade openssl sources to 1.1.1n (Richard Lau) #42348v12.22.10: 2022-02-01, Version 12.22.10 'Erbium' (LTS), @ruyadornoCompare Source
Notable changes
Commits
33899b435d] - deps: upgrade npm to 6.14.16 (Ruy Adorno) #41601d9237c46ca] - tools: update tzdata to 2021a4 (Albert Wang) #41443v12.22.9: 2022-01-10, Version 12.22.9 'Erbium' (LTS), @richardlauCompare Source
This is a security release.
Notable changes
Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)
Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.
Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the
--security-revertcommand-line option.More details will be available at CVE-2021-44531 after publication.
Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)
Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.
Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the
--security-revertcommand-line option.More details will be available at CVE-2021-44532 after publication.
Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)
Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.
Affected versions of Node.js do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.
More details will be available at CVE-2021-44533 after publication.
Prototype pollution via
console.tableproperties (Low)(CVE-2022-21824)Due to the formatting logic of the
console.table()function it was not safe to allow user controlled input to be passed to thepropertiesparameter while simultaneously passing a plain object with at least one property as the first parameter, which could be__proto__. The prototype pollution has very limited control, in that it only allows an empty string to be assigned numerical keys of the object prototype.Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.
More details will be available at CVE-2022-21824 after publication.
Thanks to Patrik Oldsberg (rugvip) for reporting this vulnerability.
Commits
be69403528] - console: fix prototype pollution via console.table (Tobias Nießen) nodejs-private/node-private#30719873abfb2] - crypto,tls: implement safe x509 GeneralName format (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300ff9ac7d757] - doc: fix date for v12.22.8 (Richard Lau) #41213a5c7843cab] - src: add cve reverts and associated tests (Michael Dawson and Akshay Kumar) nodejs-private/node-private#300d4e5d1b9ca] - src: rConfiguration
📅 Schedule: Branch creation - "after 6am and before 10am on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.