chore(deps): update all non-major dependencies #503
Conversation
This file contains hidden or 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}
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Note Free review on us!CodeRabbit is offering free reviews until Wed Jan 15 2025 to showcase some of the refinements we've made. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
25 times, most recently
from
f0a5a4b to
b164110
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
17 times, most recently
from
d97bf42 to
0342a69
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
11 times, most recently
from
ef31233 to
b35e8bd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
b35e8bd to
172c847
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:
3.0.0->3.16.07.1.0->7.6.01.0.2->1.1.010.0.1->10.2.09.0.0->9.1.01.0.0->1.2.29.1.5->9.1.716.0.0->16.1.210.2.1->10.13.17.6.3->7.7.25.7.2->5.8.33.0.0->3.5.0Release Notes
antfu/eslint-config (@antfu/eslint-config)
v3.16.0Compare Source
🚀 Features
View changes on GitHub
v3.15.0Compare Source
🚀 Features
prefer-constin editor - by @antfu (12dd5)View changes on GitHub
v3.14.0Compare Source
🚀 Features
View changes on GitHub
v3.13.0Compare Source
🚀 Features
View changes on GitHub
v3.12.2Compare Source
🚀 Features
View changes on GitHub
v3.12.1Compare Source
No significant changes
View changes on GitHub
v3.12.0Compare Source
🚀 Features
@eslint-react/eslint-pluginto ^1.19.0 - by @Rel1cx in https://github.com/antfu/eslint-config/issues/642 (a0a82)View changes on GitHub
v3.11.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.11.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.11.0Compare Source
🐞 Bug Fixes
antfu/no-top-level-awaitfor Astro - by @kidonng in https://github.com/antfu/eslint-config/issues/638 (40ee7)View changes on GitHub
v3.10.0Compare Source
🚀 Features
perfectionistto v4 - by @antfu (667c4)View changes on GitHub
v3.9.2Compare Source
🚀 Features
View changes on GitHub
v3.9.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.8.0Compare Source
🚀 Features
View changes on GitHub
v3.7.3Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.7.2Compare Source
🚀 Features
🐞 Bug Fixes
antfu/no-top-level-awaitfor markdown snippets - by @antfu (a984c)View changes on GitHub
v3.7.1Compare Source
🚀 Features
View changes on GitHub
v3.7.0Compare Source
🚀 Features
antfu/no-top-level-await- by @antfu (a08aa)🐞 Bug Fixes
explicit-function-return-typein markdown code - by @antfu (60ffd)ts/explicit-function-return-typein vue files - by @antfu (1788d)View changes on GitHub
v3.6.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.6.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.6.0Compare Source
🐞 Bug Fixes
perfectionist/sort-importssort types always on top - by @antfu (e2839)View changes on GitHub
v3.5.1Compare Source
No significant changes
View changes on GitHub
v3.5.0Compare Source
🚀 Features
🐞 Bug Fixes
unicorn/consistent-function-scoping- by @antfu (5363d)View changes on GitHub
v3.4.1Compare Source
No significant changes
View changes on GitHub
v3.4.0Compare Source
🚀 Features
@types/eslint- by @antfu (21e9c)View changes on GitHub
v3.3.2Compare Source
🐞 Bug Fixes
side-effectinperfectionist/sort-imports- by @antfu (298f3)View changes on GitHub
v3.3.1Compare Source
🐞 Bug Fixes
perfectionist/sort-imports- by @antfu (09697)View changes on GitHub
v3.3.0Compare Source
🚀 Features
perfectionist/sort-importset al, close #456 - by @antfu in https://github.com/antfu/eslint-config/issues/456 (a6efa)View changes on GitHub
v3.2.2Compare Source
🐞 Bug Fixes
unicorn/consistent-function-scopingfor arrow functions - by @antfu (362ab)View changes on GitHub
v3.2.1Compare Source
No significant changes
View changes on GitHub
v3.2.0Compare Source
🚀 Features
View changes on GitHub
v3.1.0Compare Source
🚀 Features
antfu/consistent-chaining- by @antfu (d6dfc)View changes on GitHub
sanity-io/client (@sanity/client)
v7.6.0Compare Source
Features
v7.5.0Compare Source
Features
agent.action.transformcan now transform images to text descriptions (#1096) (609e572)v7.4.1Compare Source
Bug Fixes
v7.4.0Compare Source
Features
Bug Fixes
v7.3.0Compare Source
Features
v7.2.2Compare Source
Bug Fixes
v7.2.1Compare Source
Bug Fixes
nanoidto ensure compatibility with node < 22 (#1076) (368a12d)v7.2.0Compare Source
Features
sanity-io/image-url (@sanity/image-url)
v1.1.0Compare Source
Changes
frame()methodvanityName()method (thanks @Isissss!)baseUrlin builder typings (thanks @ryami333!).format(undefined)(thanks @selbekk!)antfu-collective/bumpp (bumpp)
v10.2.0Compare Source
🚀 Features
View changes on GitHub
v10.1.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v10.1.0Compare Source
🚀 Features
View changes on GitHub
v10.0.3Compare Source
🐞 Bug Fixes
View changes on GitHub
v10.0.2Compare Source
No significant changes
View changes on GitHub
conventional-changelog/conventional-changelog (conventional-changelog-conventionalcommits)
v9.1.0Compare Source
Features
mmkal/expect-type (expect-type)
v1.2.2Compare Source
7d6fa420c9d8c27ff4f4d1149186v1.2.1Compare Source
0c5a05dv1.2.0Compare Source
What's Changed
❗
toMatchTypeOfis now deprecated. There are no plans to remove it any time soon, so it's not critical to immediately remove usages, but if you want to avoid squigglies in IDEs complaining about deprecations, here's what you should do:If you have an assertion like this:
There are a few options for upgrading it. The easiest is
toExtendwhich is identical to the behaviour oftoMatchTypeOf:This will work in all cases. But, there is now a stricter option that will work in many cases and be slightly more likely to catch things like
readonlyproperties matching:But, as the name suggests, this will only work on plain object types, it will fail for union types, and some other complex types.
If you have code like this:
You'll need to use
typeofbecausetoExtendandtoMatchObjectTypedo not accept argumentsFull Changelog: mmkal/expect-type@v1.1.0...v1.2.0
v1.1.0Compare Source
What's Changed
.toBeBigInt()by @aryaemami59 in https://github.com/mmkal/expect-type/pull/123Full Changelog: mmkal/expect-type@v1.0.0...v1.1.0
typicode/husky (husky)
v9.1.7Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.6...v9.1.7
v9.1.6Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.5...v9.1.6
lint-staged/lint-staged (lint-staged)
v16.1.2Compare Source
Patch Changes
#1570
a7c0c88Thanks @ItsNickBarry! - When using--diff-filterwith theDoption to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit addlikefatal: pathspec 'deleted-file' did not match any files.38f942eThanks @iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFilesto console output.v16.1.1Compare Source
Patch Changes
#1565
3686977Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using--no-stash.#1571
02299a9Thanks @iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.#1563
bc61c74Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stashoption. This happened because--no-stashimplied--no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.The previous (incorrect) behavior can still be achieved by using both options
--no-stash --no-hide-partially-stagedat the same time.v16.1.0Compare Source
Minor Changes
#1536
e729daaThanks @iiroj! - A new flag--no-reverthas been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.#1550
b27fa3fThanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.Patch Changes
c37dc38Thanks @iiroj! - The minimum required Node.js version is lowered to20.17following nano-spawn@1.0.2.pnpm/pnpm (pnpm)
v10.13.1Compare Source
Patch Changes
v10.13.0Compare Source
Minor Changes
Added the possibility to load multiple pnpmfiles. The
pnpmfilesetting can now accept a list of pnpmfile locations #9702.pnpm will now automatically load the
pnpmfile.cjsfile from any config dependency named@pnpm/plugin-*orpnpm-plugin-*#9729.The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the
pnpmfile.cjsfiles in the config dependencies can be explicitly listed using thepnpmfilesetting inpnpm-workspace.yaml.Patch Changes
pkg.pr.new, treat them as Git tarball URLs #9694.dangerouslyAllowAllBuilds,onlyBuiltDependencies,onlyBuiltDependenciesFile, andneverBuiltDependencies#9628.pnpm-workspace.yamlwith deep #9701.pnpm rebuildcommand should not add pkgs included inignoredBuiltDependenciestoignoredBuildsinnode_modules/.modules.yaml#9338.shell-quotewithshlexfor quoting command arguments #9381.v10.12.4Compare Source
Patch Changes
Fix
pnpm licensescommand for local dependencies #9583.Fix a bug in which
pnpm ls --filter=not-exist --jsonprints nothing instead of an empty array #9672.Fix a deadlock that sometimes happens during peer dependency resolution #9673.
Running
pnpm installafterpnpm fetchshould hoist all dependencies that need to be hoisted.Fixes a regression introduced in [v10.12.2] by [#9648]; resolves [#9689].
[v10.12.2]: https://redirect.github.com/pnpm/pnpm/releases/tag/v10.12.2Add commentMore actions
[#9648]: https://github.com/pnpm/pnpm/pull/9648
[#9689]: https://github.com/pnpm/pnpm/issues/9689
v10.12.3Compare Source
Patch Changes
Regression introduced in v10.12.2 by #9648; resolves #9685.
v10.12.2Compare Source
Patch Changes
enableGlobalVirtualStoreset totrue#9648.--helpand-hflags not working as expected for thepnpm createcommand.pnpm licenses list --jsoncommand is incorrect.pnpm deployfails due to overridden dependencies having peer dependencies causingERR_PNPM_OUTDATED_LOCKFILE#9595.v10.12.1Minor Changes
Experimental. Added support for global virtual stores. When enabled,
node_modulescontains only symlinks to a central virtual store, rather tonode_modules/.pnpm. By default, this central store is located at<store-path>/links(you can find the store path by runningpnpm store path).In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.
To enable the global virtual store, set
enableGlobalVirtualStore: truein your rootpnpm-workspace.yaml, or globally via:NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.
Related PR: #8190
pnpm updatecommand now supports updatingcatalog:protocol dependencies and writes new specifiers topnpm-workspace.yaml.--save-catalogand--save-catalog-name=<name>) topnpm addto save new dependencies as catalog entries.catalog:orcatalog:<name>will be added topackage.jsonand the package specifier will be added to thecatalogsorcatalog[<name>]object inpnpm-workspace.yaml#9425.cifor explicitly telling pnpm if the current environment is a CI or not.Patch Changes
pnpm patchusing semantic versioning rules.v10.11.1Compare Source
Patch Changes
pnpm deploy --legacycreates unexpected directories when the rootpackage.jsonhas a workspace package as a peer dependency #9550.strictPeerDependenciesistruebut all issues are ignored bypeerDependencyRules#9505.pnpm_config_env variables instead ofnpm_config_#9571.--lockfile-onlyflag onpnpm updateto produce a differentpnpm-lock.yamlthan an update without the flag.pnpm deploywork in repos withoverrideswheninject-workspace-packages=true#9283.pnpm -r --silent runshould not print out section #9563.v10.11.0Compare Source
Minor Changes
A new setting added for
pnpm initto create apackage.jsonwithtype=module, wheninit-typeismodule. Works as a flag for the init command too #9463.Added support for Nushell to
pnpm setup#6476.Added two new flags to the
pnpm auditcommand,--ignoreand--ignore-unfixable#8474.Ignore all vulnerabilities that have no solution:
> pnpm audit --ignore-unfixableProvide a list of CVE's to ignore those specifically, even if they have a resolution.
> pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678Added support for recursively running pack in every project of a workspace #4351.
Now you can run
pnpm -r packto pack all packages in the workspace.Patch Changes
dangerouslyAllowAllBuildsis set totrue#9472.pnpm linkshould work from inside a workspace #9506.workspaceConcurrencytoMath.min(os.availableParallelism(), 4)#9493.strictPeerDependenciesistruebut all issues are ignored bypeerDependencyRules#9505.updateConfigfrompnpm-workspace.yaml#9500.recursive packurl.parseusage to fix warning on Node.js 24 #9492.pnpm runshould be able to run commands from the workspace root, ifignoreScriptsis set tottrue#4858.v10.10.0Compare Source
Minor Changes
preResolution,importPackage, andfetchershooks from local pnpmfile.Patch Changes
cdcommand, whenshellEmulatoristrue#7838.pnpm-workspace.yaml#9453.npm_package_jsonenvironment variable to the executed scripts #9452.--reporter=silentoption.v10.9.0Compare Source
Minor Changes
Added support for installing JSR packages. You can now install JSR packages using the following syntax:
or with a version range:
For example, running:
will add the following entry to your
package.json:{ "dependencies": { "@​foo/bar": "jsr:^0.1.2" } }When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
{ "dependencies": { "@​foo/bar": "npm:@​jsr/foo__bar@^0.1.2" } }Related issue: #8941.
Note: The
@jsrscope defaults to https://npm.jsr.io/ if the@jsr:registrysetting is not defined.Added a new setting,
dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this topnpm-workspace.yaml:dangerouslyAllowAllBuildshas the same effect but also allows to be set globally via:It can also be set when running a command:
Patch Changes
verifyDepsBeforeRunwhennodeLinkerishoistedand there is a workspace package without dependencies andnode_modulesdirectory #9424.verifyDepsBeforeRunsupport fornodeLinker: pnp. CombiningverifyDepsBeforeRunandnodeLinker: pnpwill now print a warning.v10.8.1Compare Source
Patch Changes
package.json,onlyBuiltDependencieswill be written topnpm-workspace.yamlfile #9404.v10.8.0[Compar
Configuration
📅 Schedule: Branch creation - "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 was generated by Mend Renovate. View the repository job log.