-
Notifications
You must be signed in to change notification settings - Fork 751
fix(deps): update all npm non-major dependencies #6625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
01fae5c to
969285b
Compare
969285b to
9417749
Compare
9417749 to
34e3fb6
Compare
34e3fb6 to
5c640bd
Compare
5c640bd to
8896aa0
Compare
8896aa0 to
10efb4a
Compare
10efb4a to
8abcf38
Compare
8abcf38 to
8035fde
Compare
8035fde to
ee698a0
Compare
ee698a0 to
7cfcd21
Compare
7cfcd21 to
07e8b85
Compare
07e8b85 to
a025485
Compare
a025485 to
db9435a
Compare
8be7462 to
72f7b5e
Compare
72f7b5e to
67f487c
Compare
67f487c to
57d4645
Compare
57d4645 to
03224e1
Compare
03224e1 to
a2cecef
Compare
a2cecef to
e60822f
Compare
e60822f to
1a322b1
Compare
1a322b1 to
79af2df
Compare
79af2df to
606d1c6
Compare
606d1c6 to
702bcf3
Compare
702bcf3 to
46de59e
Compare
46de59e to
08da21b
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.0.30->^2.0.60^7.27.1->^7.28.02.2.2->2.2.5^2.0.10->^2.0.11^1.366.0->^1.378.06.0.4-alpha16->6.0.4-alpha9^3.9.0->^3.10.0^4.1.12->^4.1.14^0.5.16->^0.5.19^24.3.0->^24.7.0^19.1.12->^19.2.2^19.1.9->^19.2.14.25.1->4.25.2^0.3.1->^0.4.5^5.0.30->^5.0.60^3.33.0->^3.33.1^2.13.1->^2.15.0^0.9.3->^0.9.5^0.16.22->^0.16.23^0.2.0->^0.3.3^1.6.0->^1.8.2^0.542.0->^0.545.0^11.10.1->^11.12.0^2.11.1->^2.11.31.1.5->1.1.610.15.1->10.18.1^19.1.0->^19.2.0^19.1.1->^19.2.04.25.1->4.25.2^19.1.0->^19.2.0^19.1.1->^19.2.0^4.14.0->^4.14.1^15.6.6->^15.6.10^16.23.1->^16.25.0^2.5.6->^2.5.8^4.1.11->^4.1.12Release Notes
vercel/ai (@ai-sdk/react)
v2.0.60Compare Source
Patch Changes
v2.0.59Compare Source
Patch Changes
v2.0.58Compare Source
Patch Changes
v2.0.57Compare Source
Patch Changes
c319849]v2.0.56Compare Source
Patch Changes
b1d8458]v2.0.55Compare Source
Patch Changes
85da29e]v2.0.54Compare Source
Patch Changes
bc5ed71: chore: update zod peer depenedency versionbc5ed71]v2.0.53Compare Source
Patch Changes
d335191]v2.0.52Compare Source
Patch Changes
c56822d]930399b]v2.0.51Compare Source
Patch Changes
27645bb]v2.0.50Compare Source
Patch Changes
v2.0.49Compare Source
Patch Changes
17f9872]v2.0.48Compare Source
Patch Changes
17f9872]v2.0.47Compare Source
Patch Changes
99e2a2a: feat(provider/openai): support file and image tool resultsv2.0.46Compare Source
Patch Changes
66f69e7: Add 'default' as service tierv2.0.45Compare Source
Patch Changes
6f0644c: chore: use import * from zod/v46f0644c: chore: load zod schemas lazily6f0644c]6f0644c]v2.0.44Compare Source
Patch Changes
28215ca: fix(provider/openai): add providerExecuted flag to tool start chunksv2.0.43Compare Source
Patch Changes
fd46da1: feat(provider/openai): add new model IDsgpt-image-1-mini,gpt-5-pro,gpt-5-pro-2025-10-06v2.0.42Compare Source
Patch Changes
de5c066]v2.0.41Compare Source
Patch Changes
cd91e4b]v2.0.40Compare Source
Patch Changes
8c74f47: feat(provider/openai): add gpt-5-codex model idadca087: feat(provider/openai): local shell toolv2.0.39Compare Source
Patch Changes
5428a0d: The built in Code Interpreter tool input code is streamed intool-input-<start/delta/end>chunks.v2.0.38Compare Source
Patch Changes
v2.0.37Compare Source
Patch Changes
6075c91: feat(provider/openai): only send item references for reasoning when store: truev2.0.36Compare Source
Patch Changes
bc5ed71: chore: update zod peer depenedency versionbc5ed71]v2.0.35Compare Source
Patch Changes
99c946a]v2.0.34Compare Source
Patch Changes
v2.0.33Compare Source
Patch Changes
a617948]v2.0.32Compare Source
Patch Changes
1cf857d: fix(provider/openai): remove provider-executed tools from chat completions model01de47f: feat(provider/openai): rework file search toolv2.0.31Compare Source
Patch Changes
bb94467: feat(provider/openai): add maxToolCalls provider option4a2b70e: feat(provider/openai): send item references for provider-executed tool results643711d: feat (provider/openai): provider defined image generation tool supportbiomejs/biome (@biomejs/biome)
v2.2.5Compare Source
Patch Changes
#7597
5c3d542Thanks @arendjr! - Fixed #6432:useImportExtensionsnow works correctly with aliased paths.#7269
f18dac1Thanks @CDGardner! - Fixed #6648, where Biome'snoUselessFragmentscontained inconsistencies with ESLint for fragments only containing text.Previously, Biome would report that fragments with only text were unnecessary under the
noUselessFragmentsrule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>,<React.Fragment>B</React.Fragment>,<RenamedFragment>B</RenamedFragment>) would not havenoUselessFragmentsemitted for them.On the Biome side, instances such as these would emit
noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.
#7498
002cdedThanks @siketyan! - Fixed #6893: TheuseExhaustiveDependenciesrule now correctly adds a dependency that is captured in a shorthand object member. For example:is now correctly fixed to:
#7509
1b61631Thanks @siketyan! - Added a new lint rulenoReactForwardRef, which detects usages offorwardRefthat is no longer needed and deprecated in React 19.For example:
will be fixed to:
Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.
#7520
3f06e19Thanks @arendjr! - Added new nursery rulenoDeprecatedImportsto flag imports of deprecated symbols.Invalid example
Valid examples
#7457
9637f93Thanks @kedevked! - AddedstyleandrequireForObjectLiteraloptions to the lint ruleuseConsistentArrowReturn.This rule enforces a consistent return style for arrow functions. It can be configured with the following options:
style: (default:asNeeded)always: enforces that arrow functions always have a block body.never: enforces that arrow functions never have a block body, when possible.asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).style: "always"Invalid:
Valid:
style: "never"Invalid:
Valid:
style: "asNeeded"Invalid:
Valid:
style: "asNeeded"andrequireForObjectLiteral: trueValid:
#7510
527cec2Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using theirPascalCasenames, in addition to the existing TreeSitter-compatiblesnake_casenames.#7574
47907e7Thanks @kedevked! - Fixed 7574. The diagnostic message for the ruleuseSolidForComponentnow correctly emphasizes<For />and provides a working hyperlink to the Solid documentation.#7497
bd70f40Thanks @siketyan! - Fixed #7320: TheuseConsistentCurlyBracesrule now correctly detects a string literal including"inside a JSX attribute value.#7522
1af9931Thanks @Netail! - Added extra references to external rules to improve migration for the following rules:noUselessFragments&noNestedComponentDefinitions#7597
5c3d542Thanks @arendjr! - Fixed an issue wherepackage.jsonmanifests would not be correctly discoveredwhen evaluating files in the same directory.
#7565
38d2098Thanks @siketyan! - The resolver can now correctly resolve.ts,.tsx,.d.ts,.jsfiles by.jsextension if exists, based on the file extension substitution in TypeScript.For example, the linter can now detect the floating promise in the following situation, if you have enabled the
noFloatingPromisesrule.foo.tsbar.ts#7542
cadad2cThanks @mdevils! - Added the rulenoVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.This rule prevents the use of duplicate keys across different Vue component options such as
props,data,computed,methods, andsetup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.Invalid examples
Valid examples
#7546
a683accThanks @siketyan! - Internal data for Unicode strings have been updated to Unicode 17.0.#7497
bd70f40Thanks @siketyan! - Fixed #7256: TheuseConsistentCurlyBracesrule now correctly ignores a string literal with braces that contains only whitespaces. Previously, literals that contains single whitespace were only allowed.#7565
38d2098Thanks @siketyan! - TheuseImportExtensionsrule now correctly detects imports with an invalid extension. For example, importing.tsfile with.jsextension is flagged by default. If you are using TypeScript with neither theallowImportingTsExtensionsoption nor therewriteRelativeImportExtensionsoption, it's recommended to turn on theforceJsExtensionsoption of the rule.#7581
8653921Thanks @lucasweng! - Fixed #7470: solved a false positive fornoDuplicateProperties. Previously, declarations in@containerand@starting-styleat-rules were incorrectly flagged as duplicates of identical declarations at the root selector.For example, the linter no longer flags the
displaydeclaration in@containeror theopacitydeclaration in@starting-style.#7529
fea905fThanks @qraqras! - Fixed #7517: theuseOptionalChainrule no longer suggests changes for typeof checks on global objects.#7476
c015765Thanks @ematipico! - Fixed a bug where the suppression action fornoPositiveTabindexdidn't place the suppression comment in the correct position.#7511
a0039fdThanks @arendjr! - Added nursery rulenoUnusedExpressionsto flag expressions used as a statement that is neither an assignment nor a function call.Invalid examples
Valid examples
#7564
40e515fThanks @turbocrime! - Fixed #6617: improveduseIterableCallbackReturnto correctly handle arrow functions with a single-expressionvoidbody.Now the following code doesn't trigger the rule anymore:
v2.2.4Compare Source
Patch Changes
#7453
aa8cea3Thanks @arendjr! - Fixed #7242: Aliases specified inpackage.json'simportssection now support having multiple targets as part of an array.#7454
ac17183Thanks @arendjr! - Greatly improved performance ofnoImportCyclesby eliminating allocations.In one repository, the total runtime of Biome with only
noImportCyclesenabled went from ~23s down to ~4s.#7447
7139aadThanks @rriski! - Fixes #7446. The GritQL$...spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.#6710
98cf9afThanks @arendjr! - Fixed #4723: Type inference now recognisesindex signatures and their accesses when they are being indexed as a string.
Example
#7415
d042f18Thanks @qraqras! - Fixed #7212, now theuseOptionalChainrule recognizes optional chaining usingtypeof(e.g.,typeof foo !== 'undefined' && foo.bar).#7419
576baf4Thanks @Conaclos! - Fixed #7323.noUnusedPrivateClassMembersno longer reports as unused TypeScriptprivatemembers if the rule encounters a computed access onthis.In the following example,
memberas previously reported as unused. It is no longer reported.351bccdThanks @ematipico! - Added the new nursery lint rulenoJsxLiterals, which disallows the use of string literals inside JSX.The rule catches these cases:
#7406
b906112Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.
#7461
ea585a9Thanks @arendjr! - Improved performance ofnoPrivateImportsby eliminating allocations.In one repository, the total runtime of Biome with only
noPrivateImportsenabled went from ~3.2s down to ~1.4s.351bccdThanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.#7142
53ff5aeThanks @Netail! - Added the new nursery rulenoDuplicateDependencies, which verifies that no dependencies are duplicated between thebundledDependencies,bundleDependencies,dependencies,devDependencies,overrides,optionalDependencies, andpeerDependenciessections.For example, the following snippets will trigger the rule:
{ "dependencies": { "foo": "" }, "devDependencies": { "foo": "" } }{ "dependencies": { "foo": "" }, "optionalDependencies": { "foo": "" } }{ "dependencies": { "foo": "" }, "peerDependencies": { "foo": "" } }351bccdThanks @ematipico! - Fixed #3824. Now the option CLI--coloris correctly applied to logging too.v2.2.3Compare Source
Patch Changes
#7353
4d2b719Thanks @JeetuSuthar! - Fixed #7340: The linter now allows thenavigationproperty for view-transition in CSS.Previously, the linter incorrectly flagged
navigation: autoas an unknown property. This fix addsnavigationto the list of known CSS properties, following the CSS View Transitions spec.#7275
560de1bThanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.#7358
963a246Thanks @ematipico! - Fixed #7085, now the rulenoDescendingSpecificitycorrectly calculates the specificity of selectors when they are included inside a media query.#7387
923674dThanks @qraqras! - Fixed #7381, now theuseOptionalChainrule recognizes optional chaining using Yoda expressions (e.g.,undefined !== foo && foo.bar).#7316
f9636d5Thanks @Conaclos! - Fixed #7289. The ruleuseImportTypenow inlinesimport typeintoimport { type }when thestyleoption is set toinlineType.Example:
#7350
bb4d407Thanks @siketyan! - Fixed #7261: two characters・(KATAKANA MIDDLE DOT, U+30FB) and・(HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.#7377 [
811f47b](https:Configuration
📅 Schedule: Branch creation - "on the 1st day of the month" (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.