Repository navigation
Update dependencies (non-major) - #39
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/dependencies-(non-major)
branch
9 times, most recently
from
October 27, 2026 02:04
59b20f3 to
48039e6
Compare
renovate
Bot
force-pushed
the
renovate/dependencies-(non-major)
branch
from
October 27, 2026 06:12
48039e6 to
49511cc
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
9.2.4→9.3.13.14.13→3.14.2324.19.0→24.19.26.1.1→6.1.21.5.2→1.5.30.1.10→0.1.110.19.2→0.20.00.2.189→0.2.1910.25.4→0.25.50.25.4→0.25.51.86.0→1.90.02.9.2→2.9.52.9.2→2.9.519.3.0→19.3.119.3.0→19.3.10.40.2→0.41.08.12.0→8.13.01.1.5→1.1.60.23.45→0.23.461.0.151→1.0.1541.0.151→1.0.1540.11.0→0.11.10.11.0→0.11.11.53.1→1.54.10.7.19→0.7.201.1.6+spec-1.1.0→1.1.80.1.25→0.1.268.3.1→8.3.55.0.2→5.0.5Release Notes
TanStack/table (@tanstack/react-table)
v9.3.1Compare Source
Patch Changes
3d3648f- Refresh theAppTablecontext when theuseAppTableowner renders with new options or state, souseTableContext()consumers no longer show stale rows afterdatais replaced under a cached (React Compiler,useMemo,memo)AppTableelement.2d5f5b6,87c6bcc]:v9.2.8Compare Source
Patch Changes
f1c3409]:v9.2.6Compare Source
Patch Changes
#6611
b9b007f- Refactor bundled Intent skills into smaller entry points with references loaded for the current task. Keep core feature architecture and shared state directly discoverable, and move individual features, adapter compositions, and detailed migration guidance into references.Consumers with individual skill permissions or explicit agent mappings must replace retired feature/composition IDs with their owning entry points and refresh Intent mappings. See the Agent Skills guide for the replacement paths.
Updated dependencies [
b9b007f]:v9.2.5Compare Source
Patch Changes
e9158e7- Update TanStack Store dependencies to the latest compatible patch releases.e9158e7]:TanStack/virtual (@tanstack/react-virtual)
v3.14.23Compare Source
Patch Changes
2343004]:v3.14.22Compare Source
Patch Changes
887e971,5d51f1d]:v3.14.21Compare Source
Patch Changes
05bb4d3]:v3.14.20Compare Source
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:v3.14.19Compare Source
Patch Changes
269e8ed]:v3.14.18Compare Source
Patch Changes
f211d3a]:v3.14.17Compare Source
Patch Changes
3800fb3,cb510cb]:v3.14.16Compare Source
Patch Changes
7aa34f6,e7a0a92]:v3.14.15Compare Source
Patch Changes
28a2174,92c697f]:v3.14.14Compare Source
Patch Changes
#1301
ce57b78- fix(react-virtual): positiondirectDomUpdatesrows that mount without the owner re-renderingRows were only positioned by the owner's layout effect or the next
onChange. A row mounted by a child that re-renders on its own (local state, context, a resolved Suspense boundary) skipped both when it was fixed-size, and stayed unpositioned until the range changed. Rows are now positioned as they register throughmeasureElement, andcontainerRefpositions the rows that mounted together with the container.Updated dependencies [
43675bc,9df47a3,c644f10,2a631f4]:vitejs/vite-plugin-react (@vitejs/plugin-react)
v6.1.2Compare Source
Fix HMR for compound components (#1484)
Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.
Fix
compiler.logDiagnosticsoption not working (#1483)With
oxc-transform-react>= 0.148, thelogDiagnosticswas not working. This version fixes it and requiresoxc-transform-react>= 0.152 as a peer dependency if you are using thecompileroption.compiler.logDiagnosticsoption is now deprecated and should be swapped for the builtincompiler.reportDiagnostics.Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)
When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.
srijs/rust-crc32fast (crc32fast)
v1.5.3Compare Source
sdroege/ebur128 (ebur128)
v0.1.11Compare Source
Fixed
f64::MIN_POSITIVEinstead off64::EPSILONon targets without SSE2 flush-to-zero. Small but significantvalues were zeroed out there, making results depend on how the input was
split into
add_frames()calls and differ in the last bits from x86.modes. It was never reset and grew with the number of processed frames,
which could eventually overflow it on 32-bit platforms.
-infwhen requesting windowed loudness valuesin peak-only modes:
loudness_window()with a window of 0 andset_max_window()did not check that a loudness mode was enabled.Planar.Changed
Mode::SAMPLE_PEAK,Mode::TRUE_PEAK) no longer includethe bit of
Mode::Mand the BS.1770 biquad filter is completely skippedwhen no loudness mode is requested. This also avoids allocating the buffer
for the filtered audio in these modes.
fancy-regex/fancy-regex (fancy-regex)
v0.20.0Compare Source
Added
RegexOptionsBuilder::build_delegate_prefilterto disable building the prefilter (#282)RegexOptionsBuilder::start_bytesthat returns the first bytes that can match a pattern so you can build your own prefilter (#282)RegexOptionsBuilder::required_bytesthat returns the required bytes for a pattern to match (#287)RegexOptionsBuilder::max_prog_size/RegexBuilder::max_prog_sizeto cap the number of VM instructions emitted while compiling. Subroutine calls are inlined at compile time, so a self- or mutually-recursive pattern can expand without bound even while the recursion-depth cap is respected; this bounds the emitted instruction vector instead. Exceeding the cap returnsCompileError::PatternTooComplex. Disabled by default. (#298)delegate_size_limitanddelegate_dfa_size_limit. (#286, #309)RegexOptionsBuilder::delegate_dfa_skip_cache_capacity_check/RegexBuilder::delegate_dfa_skip_cache_capacity_check, enabled by default. Setting it tofalsemakes the reverse DFA of a variable-length lookbehind strictly honourdelegate_dfa_size_limit, so a too-small limit becomes a compile error. (#309)ByteSet::is_subsetto test whether one byte set is a subset of another. (#289)Changed
\b,\B,\<,\>) are no longer marked hard outside a lookbehind. regex-automata supports them, so a pattern like\b(?:foo|bar|baz)\bnow compiles to a single delegated engine instead of one branch per alternative — previously it grew linearly with the number of alternatives. They remain hard inside a lookbehind, since regex-automata's reverse DFA can't run a variable-length lookbehind on unicode haystacks. The half-boundary variants (\<half,\>half) and\Zare still always hard.Regex::capture_namesreports the name for each of them, and named backrefs resolve to the last group with that name (#177)Fixed
delegate_dfa_size_limit(or the default of 2 MiB); for example(?<=\p{L}{99,100})xfailed to compile with default settings. The capacity is now rounded up to the minimum required. Ordinary delegates were not affected because the meta engine falls back to another engine when the lazy DFA cannot be built. (#309)delegate_dfa_size_limitnow sets the lazy DFA cache capacity (hybrid_cache_capacity) as documented, instead of the fully compiled DFA size limit. It had been forwarded to the wrong regex-automata option since the switch from theregexcrate. (#307)\xHHescapes above0x7Fnow match the Unicode codepoint (as UTF-8 bytes) instead of the raw byte, so e.g.\xFFmatchesÿrather than the byte0xFF. In bytes modes the raw byte is matched as before. (#292)(?i)[à-ÿ]), which previously could miss candidate start positions. (#296)^/$and their multi-line variants matching at the start/end of arbitrary-byte haystacks inAsciiandUnicodeBytesbytes modes, where the match position was not a UTF-8 codepoint boundary. (#300)(a)?b(?(1)c)no longer fails to matchb. (#304)(?<=(\w+)\1)xonééx). (#310)rust-lang/libc (libc)
v0.2.191Compare Source
Support
Added
F_SETNOSIGPIPEandF_GETNOSIGPIPE(#5609)ifaliasreqandin6_aliasreq(#5557)PT_*constants (#5625)AI_*andNI_*constants from netdb.h (#5585)POSIX_SPAWN_*flags (#5578)AT_SYMLINK_NOFOLLOW(#5614)sensordev(#5534)isatty(#5618)pthread_condattr_{get,set}clock(#5626)Fixed
gpregsandfpregs(#5603)Changed
prop_infoan extern type (#5561)NOTE_PCTRLMASKwith a deprecation warning (#5600)v0.2.190Compare Source
There is now a single config for enabling 64-bit
time_t:libc_unstable_time64. This can be setunconditionally; it opts in to 64-bit
time_ton the following platforms that use 32-bit bydefault:
musl v1.2.
Most other 32-bit platforms are either already using 64-bit
time_t, or are considered legacyand will not be gaining support from their upstream maintainers.
You can enable this using
RUSTFLAGS:RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...Note that there may still be some changes to features gated by this config option, hence "unstable"
in its name. In the near future we will rename it to just
libc_time64. Until then, please test itout and report any bugs you find!
Support
Added
We are slowly filling out the
Defaultimplementations, to reduce the need formem::zeroed()in user code:Defaultfor a number of structs, especially on Apple platforms (#5576)statvfsaDefaultimpl (#5583)Defaultto alinux/can.rsstructs (#5257)Other additions:
libc_unstable_time64cfg (#5411)pthread_gettid_np(#5359)RTLD_NEXT(#5323)NET_RT_DUMP2(#5442)posix_spawn_file_actions_add(f)chdir(_np)(#5558)BPF_WORDALIGN(#5320)lchmodandlchflagswhere supported (#5400)minheritand related constants (#4849)AT_RENAME_*andRENAME_*constants (#5560)renameat2(#5563)rt_msghdrandrt_metrics(#5367)libc_unstable_gnu_time_bits(#5242)environ(#5339)f_typefield tostatvfsandstatvfs64(#5434)STATX_*constants (#5412)SIGEV_THREAD_ID(#5375)*_SUPER_MAGICconstants (#5453)statxalways available (#5448)max_align_t(#5389)BCACHEFS_SUPER_MAGIC(#5516)ETH_P_LLDP(#5438)FUTEX_ROBUST_UNLOCKandFUTEX_ROBUST_LIST32(#5525)NLMSG_*helpers (#5321)siginfo_tand add more getter functions (#5345)SYS_futex_waitv(#5527)__errno(#5346)RTLD_NODELETEandRTLD_NOLOAD(#5377)getexecpath(#5465)sensors.h(#5510)HW_*sysctl constants (#5371)FILENAME_MAX(#5530)clock_settimeandpause(#5363)getrandombindings (#5333)group_req/group_source_reqandMCAST_*where supported (#5236)HOST_NAME_MAX(#5531)_PATH_BSHELLand_PATH_DEFPATHwhere available (#5449)SOCK_CLOEXEC(#5336)time_ton 32-bit platforms via cfg (#5261)Deprecated
_kernel_simple_lock(#5380)*_MIN/*_MAXin favor of e.g.c_int::MAX(#5404)fallocate64, which does not exist on the platform (#5242)glob64types and routines (#5242)syscall,mincore, andKERN_NSELCOLL, all of which have been removed upstream (87992e9895c2)tmpnam,tempnam(#5478)Fixed
BPF_ALIGNMENTtosize_tto match upstream and harmonize with other platforms. (#5373)BPF_ALIGNMENTtosize_tto match upstream and harmonize with other platforms. (#5348)fileops_t.fo_select(#5380)file(#5380)ucontext_t(#5189)O_flags (#5554)mcontext_tanducontext_tand make them usable on more platforms (#5127)glob_tandstatvfs(#5127)sigeventand correct the layout of otherpthread.htypes (#5127)sem_t(#5351)statvfs64on 32-bit RISC-V (#5518)ipc_perm(#5527)uc_flagsfield inucontext_t(#5527)WIFSTOPPED(#5458)time_talias. This is a correction on Arm32 RTEMS (#5132)O_open flags (#5414)socket.hdefinitions (#5313)signal.htypes (#5436)Changed
libc_unstable_musl_v1_2_3has been renamed to a more accuratelibc_unstable_musl_v1_2. The old version will continue to work for now, but will be removed in1-2 releases. (#5376)
unsafe(#5380)POSIX_SPAWN_*flags toc_short(#5572)FD_*functions (#5528)__riscv_mc_q_ext_state.__reservedand make it private (#5533)statfields non-pub(#5542)Removed
libcexposed quite a bit of API on all Apple platforms that is not actually available anywhere other than MacOS. This release removes a number of these cases.mach.hAPI on Apple mobile OSs (e6bfb187513c)exec*andforkcalls from tvOS and watchOS (#5158)Additionally, this release cleans up a lot of API that has been deprecated since at least libc 0.2.100, released 2021-08-20.
af_alg_ivtrait implementations. The have been deprecated for a long time because they allowed out-of-bounds reads via safe functions. (444db4456f38)Other removed items:
INHERIT_ZEROthat does not exist upstream (#5587)REG_*definitions (#5527)REG_NARGS(#5527)A huge thank you to our GSoC student Adam Martinez (@dybucc) who did a
huge amount of the time64 work, as well as many of the platform fixes!
Serial-ATA/lofty-rs (lofty)
v0.25.5Compare Source
Added
GlobalOptions::preserve_format_specific_items()(PR)WriteOptions::preferred_padding()(PR)GlobalOptions::preserve_format_specific_items()(PR)GlobalOptions::preserve_format_specific_items()(PR)Fixed
ItemKey::{Work, FlagCompilation, FlagPodcast}conversions (issue) (PR)COMTchunks with padding (issue) (PR)ilstatom (PR)remove_from_path()no longer opens the file in read-only mode (issue) (PR)oxc-project/oxc (oxlint)
v1.90.0Compare Source
🚀 Features
831cdf1oxlint: Require mininum oxlint-tsgolint version v7.0.2005 (#28118) (camc314)d1b00f4linter/typescript: Implement no-unsafe-enum-assignment rule (#28117) (camc314)165c91flinter/typescript/await-thenable: SupportallowMixedPromiseArraysoption (#28116) (camc314)v1.89.0Compare Source
🐛 Bug Fixes
9a424c2oxlint,oxfmt: Correct Node.js TypeScript support range (#27699) (camc314)v1.88.0Compare Source
🚀 Features
3c361a7linter/unicorn/prefer-query-selector: AddallowWithVariablesoption (#27346) (Mikhail Baev)v1.87.0: oxlint v1.87.0Compare Source
🚀 Features
42dcfd2linter/react/no-unescaped-entities: Implement suggestion (#27292) (Mikhail Baev)cd4510dlinter/unicorn/no-useless-switch-case: Implement suggestion (#27245) (Mikhail Baev)1a7c902linter/react/jsx-no-target-blank: Implement suggestion (#27181) (Mikhail Baev)🐛 Bug Fixes
176b4b9linter/jsx-a11y/label-has-associated-control: Validate label attribute values (#27302) (sama Pyb)7d381c3linter/jsx-a11y/mouse-events-have-key-events: Handle nullish event handlers (#27306) (sama Pyb)4e09837linter/jsx-a11y/lang: Validate lang expression strings (#27304) (sama Pyb)7d28a66linter/unicorn/numeric-separators-style: Report misgrouped BigInt literals (#27207) (breken)e928322linter/unicorn/no-zero-fractions: Parenthesize separator and large integers in fixer (#27206) (breken)3d61a59parser: Validate TypeScript type member separators (#27222) (camc314)f08236blinter/eslint/prefer-exponentiation-operator: Preserve autofix precedence (#27150) (camc314)7d60ae3linter/valid-title: Continue checks after allowed words (#27146) (Cameron)ad5dd5dlinter/eslint/no-unused-vars: Respect disabled argument checks for used ignore patterns (#26925) (camc314)pest-parser/pest (pest)
v2.9.5Compare Source
What's Changed
Full Changelog: pest-parser/pest@v2.9.4...v2.9.5
Warning: Semantic Versioning
Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated
Ruleenum.This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:
pest 2.9.3 and 2.9.4 required a
stackerdependency which relies on a C compiler toolchain; this was made optional for non-native targets and can be opt-in enabled with the feature flag in those targets (see native stack guard notes in README):v2.9.4Compare Source
What's Changed
New Contributors
Full Changelog: pest-parser/pest@v2.9.3...v2.9.4
Warning: Semantic Versioning
Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between mino
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 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.