Update all non-major dependencies - #4222
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 1, 2026 18:04
a20ad31 to
b6fd90a
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 2, 2026 01:15
b6fd90a to
c3cdf7e
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 2, 2026 05:46
c3cdf7e to
c772bd1
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 2, 2026 23:13
c772bd1 to
28f32b4
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 3, 2026 12:24
28f32b4 to
7c9cb31
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 3, 2026 18:24
7c9cb31 to
605ae02
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 4, 2026 01:37
605ae02 to
e7f97fc
Compare
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
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:
1.62.0→1.62.110.5.5→10.5.1010.6.010.5.5→10.5.1010.6.010.5.5→10.5.1010.6.016.3.2→16.3.314.6.1→14.6.614.6.719.2.17→19.2.1819.2.3→19.2.519.2.7(+1)8.65.0→8.68.08.69.06.0.5→6.1.14.1.10→4.1.114.1.10→4.1.114.1.10→4.1.1110.5.5→10.5.1010.6.026.3.6→26.4.026.4.2(+1)1.67.3→1.71.31.73.0(+5)v1.13.4→v1.13.6^0.61.0→^0.65.00.66.01.76.0→1.80.01.81.08.5.25→8.5.268.5.28(+1)7.18.2→7.18.31.102.0→1.103.11.104.010.5.5→10.5.1010.6.014.0.1→14.0.28.1.5→8.2.24.1.10→4.1.11Release Notes
microsoft/playwright (@playwright/test)
v1.62.1Compare Source
storybookjs/storybook (@storybook/addon-docs)
v10.5.10Compare Source
v10.5.9Compare Source
v10.5.8Compare Source
v10.5.7Compare Source
v10.5.6Compare Source
@testing-library/jest-domto6.9.1- #35614, thanks @ndelangen!storybookjs/storybook (@storybook/addon-vitest)
v10.5.10Compare Source
v10.5.9Compare Source
v10.5.8Compare Source
v10.5.7Compare Source
v10.5.6Compare Source
@testing-library/jest-domto6.9.1- #35614, thanks @ndelangen!storybookjs/storybook (@storybook/react-vite)
v10.5.10Compare Source
v10.5.9Compare Source
v10.5.8Compare Source
v10.5.7Compare Source
v10.5.6Compare Source
@testing-library/jest-domto6.9.1- #35614, thanks @ndelangen!testing-library/react-testing-library (@testing-library/react)
v16.3.3Compare Source
Bug Fixes
testing-library/user-event (@testing-library/user-event)
v14.6.6Compare Source
Bug Fixes
v14.6.5Compare Source
Bug Fixes
v14.6.4Compare Source
v14.6.3Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/utils)
v8.68.0Compare Source
🚀 Features
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.67.0Compare Source
This was a version bump only for utils to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.66.0Compare Source
This was a version bump only for utils to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
vitejs/vite-plugin-react (@vitejs/plugin-react)
v6.1.1Compare Source
Add
compiler.logDiagnosticsoptionRecoverable React Compiler diagnostics are no longer logged by default. Set
compiler.logDiagnosticstotrueto log them through Vite. Fatal diagnostics are always logged and fail the transform.Respect environment sourcemap option for React Compiler transform when
builder.sharedPluginsis enabled (#1439)The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental
builder.sharedPluginswas enabled.v6.1.0Compare Source
Add experimental native React Compiler support (#1419)
Add experimental native React Compiler support.
You can use it by installing
oxc-transform-reactand enabling it via thecompileroption:vitest-dev/vitest (@vitest/browser-playwright)
v4.1.11Compare Source
🐞 Bug Fixes
View changes on GitHub
storybookjs/storybook (eslint-plugin-storybook)
v10.5.10Compare Source
v10.5.9Compare Source
v10.5.8Compare Source
v10.5.7Compare Source
v10.5.6Compare Source
@testing-library/jest-domto6.9.1- #35614, thanks @ndelangen!i18next/i18next (i18next)
v26.4.0Compare Source
toResolveHierarchyresults per(code, fallbackCode)pair. The hierarchy resolver runs on everyt()call and callsIntl.getCanonicalLocalesmultiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically whenoptions.fallbackLngchanges (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load,lowerCaseLng,cleanCode,nonExplicitSupportedLngs), calli18next.services.languageUtils.clearCache()afterwards. Function-valuedfallbackLngand per-call array/objectfallbackLngoptions are never cached, so dynamic fallbacks keep working as before. Thanks @equaterina (#2444).@rollup/plugin-babelsupports 8, eslint on 9.x for neostandard). Removed the unusedcoverallspackage (CI uses the Coveralls GitHub Action) and replacedsinonwithnise+vitest.spyOnin the v1 compatibility tests, which resolves all opennpm auditfindings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.i18next/i18next-cli (i18next-cli)
v1.71.3Compare Source
fallbackNSaccounting now works when the fallback namespace lives in its own fileoutside a merged output (
mergeNamespaces: true), e.g. split out and hidden viaignoreNamespaces:statusandextractlook up a fallback namespace missing from themerged file at its per-namespace path, and a function
outputresolves the merged filewithout a namespace (matching what
extractwrites), so hybrid layouts are expressible viaan
outputfunction. When afallbackNSis listed inignoreNamespacesbut itstranslations cannot be found,
statusnow warns instead of silently reporting the keys asabsent (#287).
v1.71.2Compare Source
extractno longer scales quadratically with the number of keys: selector-API /returnObjectskeys are matched via an O(key depth) Set lookup instead of one regex perobject key, and the per-key leaf check uses a precomputed ancestor-prefix Set instead of
scanning all keys. A 4-minute run on a ~11,500-key monorepo drops to seconds; written
output is byte-identical (#286).
v1.71.1Compare Source
.reduce()/.reduceRight()over anas constarray now bind the element callbackparameter (the second one,
(acc, el) => …) like.map()/.forEach()already did, soERRORS.reduce((acc, n) => { acc[n] = t(`errors.${n}.title`) }, {})extracts every elementwithout the
(typeof ERRORS)[number]cast workaround(#285).
v1.71.0Compare Source
status.ignoreKeysconfig option: glob patterns (same shape aspreservePatterns,optional
ns:prefix) for keys thatstatusshould not report or fail on, e.g. keys that areintentionally empty in some locales. Only affects
status;extractis unchanged(#284).
v1.70.4Compare Source
useTranslation(ns)wherensis a function parameter now resolves to the parameter'sstring default (
({ ns = 'a' }) =>,(ns = 'a') =>), or, without a default, to the firstmember of its inline union type (
{ ns: 'a' | 'b' }), mirroring theTFunction<'a' | 'b'>rule (#284).
v1.70.3Compare Source
TFunction<Ns>members are now found inside intersection types(
Base & { t?: TFunction<Ns> }), including optionalt?:and overload implementationsignatures (#284).
TFunction<Namespace>,<Ns extends Namespace>) are no longerresolved to their first member. Introduced in 1.70.2, this could attribute keys to an arbitrary
namespace when the alias is an app-wide union. Inline unions and literal generic constraints still
resolve to the first member.
v1.70.2Compare Source
(#284):
TFunction<'a' | 'b'>,TFunction<Ns>with<Ns extends 'a' | 'b'>, andTFunction<Alias>with a local
type Alias = 'a' | 'b'resolve to the first member (plain, destructured andprops.tmember-call forms).useTranslation(['a', 'b'] as const)anduseTranslation(NS)with a localconst NS = ['a', 'b']are resolved like the inline array form.v1.70.1Compare Source
(#284):
ReturnType<typeof useTranslation<'ns', 'keyPrefix'>>['t']on parameters (plain anddestructured) is treated like
TFunction<'ns', 'keyPrefix'>.translation function (e.g.
const t = useCallback((key, opts) => tLocal(key, opts), [...]))inherits that function's namespace / keyPrefix.
t()calls inside fenced code blocks (```) of doc comments are no longer extractedas real call sites.
v1.70.0Compare Source
tfunctions whose namespace is not a plainuseTranslation('ns')literal (#284):useTranslation(ns ?? 'fallback')/useTranslation(ns || 'fallback')now resolve to thestatically known side (the fallback literal when the left side is dynamic) instead of
silently falling back to
defaultNS.TFunction<'ns'>/TFunction<'ns', 'keyPrefix'>is now honoured on destructuredparameters as well (
({ t }: { t: TFunction<'ns'> }),({ t }: Props)with a localinterface or type alias), not only on plain
(t: TFunction<'ns'>)parameters.These previously caused
status/extractto attribute such keys to the default namespaceand report them as missing.
v1.69.2Compare Source
@swc/core1.16, which types function, arrow and methodbodies as
FunctionBodyinstead ofBlockStatement(plain blocks likeif (x) { … }areunchanged). Every "is this a function body?" check silently went false, which broke selector
calls with a block body (
t($ => { return $.a.b })), return-type inference from a functionbody (finite dynamic keys), and React component-boundary detection in the instrumenter — so
useTranslation()/<Trans>were no longer injected. Both node types are now accepted.v1.69.1Compare Source
resolved by searching the raw source text, so a short string was reported at the first place
it appeared as a substring anywhere in the file — e.g.
<span>in</span>on line 4 was reportedon line 1 because of
import './settings.scss'. Lines are now taken from the AST node's span,falling back to the text search only when no span is available. This also fixes
i18next-instrument-ignore/i18next-instrument-ignore-next-linebeing ignored for suchstrings, since the directives suppress issues by line
(#283).
v1.69.0Compare Source
acceptedTags: 'all'to lint every JSX tag, including customcomponents, instead of the recommended built-in tag list. Useful together with
acceptedAttributesin codebases with many custom JSX elements where maintaining anexplicit tag accept-list is impractical.
ignoredTagsandtransComponentsstill takeprecedence, and the default behavior when
acceptedTagsis unset is unchanged(#282).
v1.68.0Compare Source
--unusedto report only unused translation keys — keys present in thetranslation files but no longer used in the source code. "Unused" is defined as what
extractwithremoveUnusedKeyswould delete: the report runs the extractor in dry-runmode (with
removeUnusedKeysforced on, regardless of the config) and diffs the existingkey set against the pruned result, so it inherits all of extract's edge-case handling
(plural variants, context variants,
preservePatterns,ignoreNamespaces). The commandnever modifies any files and exits with a non-zero status code when unused keys are found
(or when source files failed to parse, since that could cause false positives), making it
a dedicated CI check alongside the missing-translations check
status <locale>. Combineswith the locale argument and
--namespace, e.g.i18next-cli status en --unused. Notethat static analysis cannot detect dynamically constructed keys; to find keys that are
truly unused at runtime, see https://www.locize.com/docs/guides/find-unused-translations
(#281).
v1.67.9Compare Source
defaultNSfrom the generated resources whenextract.defaultNSisfalse. i18next's type system cannot expressdefaultNS: false—DefaultNamespace = TypeOptions['defaultNS']feedsNs extends Namespace, so emittingfalsemade everyt()call silently accept any string and the generated definitions checked nothing. Thenamespace is now taken from the keys of the generated
Resourcesinterface (deduplicatedand sorted, preferring
'translation', and preferring a namespace insidetypes.basePathover one resolved outside of it), with a warning naming the pick.
falseis still emittedwhen the resource files are named after locales (
en.json+de.json), where derivingwould turn sibling languages into namespaces. Only affects
i18next.d.tson firstcreation;
resources.d.tsand--cibehavior are unchanged(#280).
v1.67.8Compare Source
extractis idempotent. Thecomparator compared base keys for plural/plural pairs but full keys for every other
pair, which produced a cycle (
foo_solved < foo_zero < foo_one < foo_other < foo_solved)for a key that has both plural forms and a context variant in a locale with a
zeroplural (lv, ru, pl, lt, uk, …). The resulting order then depended on the input order, so
the same file flipped key order back and forth on every extract/download cycle. Keys are
now always compared by base key first, then by variant rank (plain key, cardinal plurals,
ordinal plurals) (#279).
iterated array.
function f(items: IProps[])withitems.map(({ size }) => t(`some_${size}`))now expands to one key per union member,as does member access on the callback element (
items.forEach(item => t(`some_${item.size}`))) and a typed array variable (const items: IProps[] = …).Covers
T[],Array<T>andReadonlyArray<T>formap/forEach/flatMap/filter/find/some/every(#210).v1.67.7Compare Source
t()call. Atop-level config/registry literal (
export const SECTIONS = [{ label: 'Appearance' }])used to be rewritten to
i18next.t(...)— evaluated once when the module is firstimported, so it may run before i18next is initialized and never updates on language
change. Such candidates are now left untouched and reported with a warning pointing at
the hook alternative. Strings inside plain (non-component) functions are still
instrumented with
i18next.t()as before(#278).
import i18next from 'i18next'is no longer appended to thesame line as a semicolon-terminated import
(
import { X } from "./x";import i18next from 'i18next'). The insertion point now movespast the end of the line, and a leading newline is added when the last import ends at
EOF without one (#278).
v1.67.6Compare Source
abc.tsx) no longer aborts the run withEISDIR: illegal operation on a directory, read. Source-file globs now passnodir: true, which also covers the extractor andthe instrumenter (#277).
v1.67.5Compare Source
line/columnin plugin location metadata for files containingmulti-byte characters (em dashes, accented letters, CJK, emoji). SWC reports AST spans
as UTF-8 byte offsets, but the extractor treated them as JavaScript string indices, so
every multi-byte character shifted all following locations. The span base was also
computed by mixing a byte offset with a character index, which additionally skewed
locations in files whose leading comments contain multi-byte characters — that part
affected the linter and instrumenter too
(#276).
v1.67.4Compare Source
interface- or object-typed function parameter.
interface IProps { size: ChangeType }with
function f({ size }: IProps) { return t(`some_${size}`) }now expands to one keyper union member. Covers destructured props (including renamed and defaulted ones),
member access on the parameter itself (
t(`some_${props.size}`)), object type aliases(
type Props = { size: 'x' | 'y' }) and inline type literals. Bindings are scoped to thefunction, so nothing leaks to same-named identifiers elsewhere
(#210).
livekit/livekit (livekit/livekit-server)
v1.13.6Compare Source
Added
Changed
f234b53(#4785)Fixed
[
v1.13.5](https://redirConfiguration
📅 Schedule: (UTC)
* 0-3 1 * *)🚦 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.