lara
lara copied to clipboard
Bump got and npm-check-updates in /src/LaraClient
Bumps got and npm-check-updates. These dependencies needed to be updated together.
Updates got from 9.6.0 to 12.3.0
Release notes
Sourced from got's releases.
v12.3.0
- Add
.off()method for events (#2092) 88056behttps://github.com/sindresorhus/got/compare/v12.2.0...v12.3.0
v12.2.0
- Support
AbortController(#2020) 6a6d2a9- Add
enableUnixSocketsoption (#2062) 461b3d4https://github.com/sindresorhus/got/compare/v12.1.0...v12.2.0
v12.1.0
Improvements
- Add
response.ok(#2043) 22d58fb
- This is only useful if you have
{throwHttpErrors: false}Fixes
- Do not redirect to UNIX sockets (#2047) 861ccd9
https://github.com/sindresorhus/got/compare/v12.0.4...v12.1.0
v12.0.4
- Remove stream lock - unreliable since Node 17.3.0 bb8eca924c338ca12d5b90d6a26aa28dbddb42ee
v12.0.3
- Allow more types in the
jsonoption (#2015) eb045bfhttps://github.com/sindresorhus/got/compare/v12.0.2...v12.0.3
v12.0.2
- Fix
encodingoption with{responseType: 'json'}(#1996) 0703318https://github.com/sindresorhus/got/compare/v12.0.1...v12.0.2
v12.0.1
- Fix
nockcompatibility (#1959) bf39d2c- Fix missing export of
RequestTypeScript type (#1940) 0f9f2b8https://github.com/sindresorhus/got/compare/v12.0.0...v12.0.1
v12.0.0
Introducing Got v12.0.0 :tada:
Long time no see! The latest Got version (v11.8.2) was released just in February ❄️ We have been working hard on squashing bugs and improving overall experience.
... (truncated)
Commits
e032b6012.3.088056beAdd.off()method for events (#2092)c41a98aMeta tweaks54e00f312.2.06a6d2a9SupportAbortController(#2020)3207061Fixcipherstest461b3d4AddenableUnixSocketsoption (#2062)d4c2913Upgrade dependencies2300514Document maintenance commitment for v1109e8273Rephrase to avoid confusion around303redirects- Additional commits viewable in compare view
Updates npm-check-updates from 12.0.2 to 16.0.5
Release notes
Sourced from npm-check-updates's releases.
v16.0.0
Breaking
- Automatic detection of package data on stdin has been removed. This feature was deprecated in
v14.0.0. Add--stdinfor old behavior. (#136)- 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. (#1168)v15.0.0
Breaking
- node >= 14.14 is now required (#1145)
- Needed to upgrade
update-notifierwith 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
--packageManageris not given, there is nopackage-lock.jsonin the current folder, and there is ayarn.lockin an ancestor directory, npm-check-updates will now use yarn.- More practically, if you needed to specify
--packageManager yarnexplicitly before, you may not have to nowv14.1.0
Features
Group
You can now group upgrades by risk level using
--format group:Interactive Mode
Interactive mode was completely rewritten for a better user experience.
Inspired by npm-check.
Combine with
--format groupfor a truly luxe experience:Static Registry
A new option
--packageManager staticRegistryallows upgrades to be recommended from a static JSON file. This can be used to power custom versioning infrastructure that is completely independent from the npm registry.Thanks to agrouse who did a fine job on the PR.
Example:
$ ncu --packageManager staticRegistry --registry ./my-registry.jsonmy-registry.json:
... (truncated)
Commits
f53d05316.0.5463d381Deep mode: Read npm config from each project directory. (#1177)f7e8c7016.0.48f40c72Doctor: Handle failed prepare script (#1175)bb8820a16.0.35c2d536Bump dependencies1e9fff9Fix --deep tests so they do not conflict with .ncurc.5f3a02916.0.22a8295freadNpmConfig: Make cafile synchronous to fix regression (#636).1b23eb8Add interactive group to ncurc.- Additional commits viewable in compare view
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.