documentation
documentation copied to clipboard
chore(deps): bump the npm_and_yarn group in /legacy with 3 updates
Bumps the npm_and_yarn group in /legacy with 3 updates: got, npm-check-updates and cacheable-request.
Updates got
from 11.8.1 to 11.8.5
Release notes
Sourced from got's releases.
v11.8.5
- Backport security fix https://github.com/sindresorhus/got/commit/861ccd9ac2237df762a9e2beed7edd88c60782dc
https://github.com/sindresorhus/got/compare/v11.8.4...v11.8.5
v11.8.3
- Bump cacheable-request dependency (#1921) 9463bb6
- Fix
HTTPError
missing.code
property (#1739) 0e167b8https://github.com/sindresorhus/got/compare/v11.8.2...v11.8.3
v11.8.2
- Make the
dnsCache
option lazy (#1529) 3bd245f This slightly improves Got startup performance and fixes an issue with Jest.https://github.com/sindresorhus/got/compare/v11.8.1...v11.8.2
Commits
5e17bb7
11.8.5bce8ce7
Backport 861ccd9ac2237df762a9e2beed7edd88c60782dc8ced192
Fix build670eb04
11.8.420f29fe
Backport #1543: Initialize globalResponse in case of ignored HTTPError (#2017)0da732f
11.8.39463bb6
Bump cacheable-request dependency (#1921)0e167b8
HTTPError code set to 'HTTPError' #1711 (#1739)f896aa5
11.8.23bd245f
Instantiate CacheableLookup only when needed (#1529)- See full diff in compare view
Updates npm-check-updates
from 7.0.2 to 16.14.18
Release notes
Sourced from npm-check-updates's releases.
v16.14.0
Feature
- Added experimental support for bun package manager.
- Automatically used if
bun.lockb
is detected.- Assistance needed to test it out on different platforms.
$ ncu --packageManager bun $ ncu -p bun
Thanks to
@ImBIOS
for the PR!v16.13.0
Feature
- Added
--install
option to control auto-install behavior.Usage:
ncu --install [value]
Default: prompt
Control the auto-install behavior.
v16.10.0
Feature
- Added
filterResults
option to filter out upgrades based on a user provided function.
filterResults
runs after new versions are fetched, in contrast tofilter
andfilterVersion
, which run before. This allows you to filter out upgrades withfilterResults
based on how the version has changed (e.g. a major version change).Only available in .ncurc.js or when importing npm-check-updates as a module.
/** Filter out non-major version updates. @param {string} packageName The name of the dependency. @param {string} currentVersion Current version declaration (may be range). @param {SemVer[]} currentVersionSemver Current version declaration in semantic versioning format (may be range). </tr></table>
... (truncated)
Changelog
Sourced from npm-check-updates's changelog.
Changelog
This file documents all major version releases. For other releases, please read the commit history.
[16.0.0] - 2022-07-23
Breaking
- Automatic detection of package data on stdin has been removed. This feature was deprecated in
v14.0.0
. Add--stdin
for old behavior.- Wild card filters now apply to scoped packages. Previously,
ncu -f '*vite*'
would not include@vitejs/plugin-react
. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.https://github.com/raineorshine/npm-check-updates/compare/v15.3.4...v16.0.0
[15.0.0] - 2022-06-30
Breaking
- node >= 14.14 is now required (#1145)
- Needed to upgrade
update-notifier
with has a moderate severity vulnerability- yarn autodetect has been improved (#1148)
- This is a patch, though technically it is breaking. In the obscure case where
--packageManager
is not given, there is nopackage-lock.json
in the current folder, and there is ayarn.lock
in an ancestor directory, npm-check-updates will now use yarn.- More practically, if you needed to specify
--packageManager yarn
explicitly before, you may not have to nowhttps://github.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0
[14.0.0] - 2022-06-16
Breaking
Prerelease versions are now "upgraded" to versions with a different preid.
For example, if you have a dependency at
1.3.3-next.1
and the version fetched by ncu is1.2.3-dev.2
, ncu will suggest an "upgrade" to1.2.3-dev.2
. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.Since this change affects only prereleases, there is no impact on default
ncu
usage that fetches thelatest
version. With--pre 1
or--target newest
or--target greatest
, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new--target @[tag]
feature.If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.
Features
- You can now upgrade to a specific tag, e.g.
--target @next
. Thanks to IMalyugin.https://github.com/raineorshine/npm-check-updates/compare/v13.1.5...v14.0.0
[13.0.0] - 2022-05-15
Breaking
- node >= 14 is now required
- Several options which have long been deprecated have been removed:
--greatest
- Instead use--target greatest
... (truncated)
Commits
522a3b1
16.14.183b9586b
fix: Add types of semver-utils (#1387)74184a1
16.14.1780e3d05
Fix peer dependencies for versions with range operators (#1378).0126a8f
16.14.16c09c380
READMEffeeee4
16.14.15fae7f11
comment29f0e51
Supportsemver
target withgitTags
package manager (#1368)9803875
16.14.14- Additional commits viewable in compare view
Updates cacheable-request
from 6.1.0 to 7.0.4
Commits
- See full diff in compare view
Maintainer changes
This version was pushed to npm by jaredwray, a new releaser for cacheable-request since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) -
@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) -
@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) -
@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency -
@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot rebase