chore(deps): update well known #1807
Open
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:
4.3.4->4.4.311.1.1->11.3.27.7.2->7.7.31.22.19->1.22.22Release Notes
debug-js/debug (debug)
v4.4.3Compare Source
Functionally identical release to
4.4.1.Version
4.4.2is compromised. Please see #1005.v4.4.1Compare Source
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.4.0...4.4.1
v4.4.0Compare Source
Fixes (hopefully) the inefficient regex warnings in
.enable().Minor version as this is invariably going to break certain users who misuse the
.enable()API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.Full Changelog: debug-js/debug@4.3.7...4.4.0
v4.3.7Compare Source
What's Changed
Full Changelog: debug-js/debug@4.3.6...4.3.7
v4.3.6Compare Source
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.5...4.3.6
v4.3.5Compare Source
Patch
cac39b1Fix/debug depth (#926)Thank you @calvintwr for the fix.
jprichardson/node-fs-extra (fs-extra)
v11.3.2Compare Source
UnhandledPromiseRejectionWarningthat could occur when calling.copy()in some cases (#1056, #1058)v11.3.1Compare Source
move/moveSynccould incorrectly think files are identical on Windows (#1050)v11.3.0Compare Source
fsmethods (#1044, #1045)fs.opendirincopy()/copySync()for better perf/scalability (#972, #1028)v11.2.0Compare Source
async/await(#1020)npm/node-semver (semver)
v7.7.3Compare Source
Bug Fixes
e37e0ca#813 faster paths for compare (#813) (@H4ad)2471d75#811 x-range build metadata support (i529015)Chores
8f05c87#807 bump @npmcli/template-oss from 4.25.0 to 4.25.1 (#807) (@dependabot[bot], @owlstronaut)yarnpkg/yarn (yarn)
v1.22.22Compare Source
Fixes a punycode warning.
Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.
v1.22.21Compare Source
Fixes an issue in the v1.22.20 when calling Yarn from a project subfolder, outside of a Corepack context.
Added a
SKIP_YARN_COREPACK_CHECKenvironment variable to skip the Corepack check.v1.22.20Compare Source
Important: Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.
A message will be displayed when Yarn 1.22 notices that the local project has a package.json file referencing a non-1.x Yarn release via the
packageManagerfield. The message will explain that the project is intended to be used with Corepack.The
yarn-error.logfiles won't be generated anymore, as we don't process non-critical 1.x bug reports (we however process all bugs reported on https://github.com/yarnpkg/berry; we just released the 4.0.2 release there).The
yarn set version x.y.zcommand will now install the exactx.y.zversion (prior to this change it used to first install the latest version, and only in a second step would it downgrade tox.y.z; this was causing issues when we bump the minimal Node.js version we support, as runningyarn set version 3.6.4wouldn't work on Node 16).Prevents crashes when reading from an empty
.yarnrc.ymlfile.Configuration
📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) (UTC), 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.