Repository navigation
fix(deps): update patch - #799
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
Contributor
Author
|
🦜 ChachalogNo changelog entries detected. Learn more about Chachalog. Create a new entry online or run |
commit: |
renovate
Bot
force-pushed
the
renovate/patch
branch
3 times, most recently
from
September 24, 2026 22:06
716de0a to
fdfc342
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
3 times, most recently
from
October 1, 2026 05:00
5f543dd to
fda1f44
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
8 times, most recently
from
October 9, 2026 13:04
2b01b06 to
ac535ab
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
10 times, most recently
from
October 14, 2026 16:22
1948dce to
1c53c3c
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
11 times, most recently
from
October 26, 2026 14:35
a443b8e to
cf36ea9
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
9 times, most recently
from
November 2, 2026 11:13
5df34a5 to
36f4f25
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
6 times, most recently
from
November 8, 2026 17:07
aad53da to
8642b07
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
2 times, most recently
from
November 12, 2026 11:52
8817ffb to
32eb59c
Compare
renovate
Bot
force-pushed
the
renovate/patch
branch
from
November 17, 2026 01:15
32eb59c to
7753bea
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:
0.5.6→0.5.71.8.1→1.9.05.19.1→5.30.28.5.0→8.9.05.4.0→5.5.122.20.3→22.20.52.0.5→2.1.07.3.3→7.4.06.0.0→6.0.37.0.2→7.0.517.12.0→17.14.017.0.2→17.1.026.4.2→26.7.21.4.1→1.4.5^0.0.88→^0.0.933.9.7→3.10.13.0.2→3.1.00.3.24→0.3.2517.0.14→17.1.131.2.9→1.3.24.0.0→4.0.10.23.0→0.23.75.2.0→5.3.08.3.0→8.3.8Release Notes
GauBen/chachalog (@chachalog/types)
v0.5.7Compare Source
releaseBranchtorelease-<branch>instead ofrelease/<branch>for non-main branches, as the latter cannot be pushed while areleasebranch exists.bombshell-dev/clack (@clack/prompts)
v1.9.0Compare Source
Minor Changes
#596
cbeefcbThanks @dreyfus92! - Add accessible mode tospinner: when enabled via theaccessibleoption, the global setting, or theACCESSIBLEenv var, the spinner emits static, append-only, screen-reader friendly output, a plain start line, a "still working" heartbeat every 30 seconds, and a plain final line. Instead of animated in-place repaints.#614
5ac9e73Thanks @btea! - Allowmultiselectto accept readonly option arrays, e.g. options declared withas const. TheValuetype parameter is now inferred as a literal union ('a' | 'b') from such arrays, andinitialValuesalso accepts readonly arrays.#622
1835f41Thanks @btea! - Add support for disabledselectKeyoptions: they are rendered dimmed, cannot be selected by keypress, and are ignored when set as the initial value.Patch Changes
#610
be35482Thanks @43081j! - Update sisteransi to 2.x (ESM only).#618
3e0bffdThanks @btea! - Use an explicit undefined check when forwarding autocomplete initialValue so 0, false, and empty strings remain selectable instead of falling back to the first option.#631
9053625Thanks @43081j! - Account for escape sequences in prefixes during line wrapping. Very narrow outputs will now render correctly.#616
f325a53Thanks @btea! - Fix that isCancelled returned after calling cancel and start methods in progress does not refresh.#627
34976a7Thanks @b84330808! - Fix thepathprompt indirectorymode on Windows: typing a trailing\after a directory now lists its children instead of showing no matches.#628
85f6affThanks @imharjot! - Render falsy primitive options through thelimitOptionsstyle callback instead of leaving blank rows.Updated dependencies [
be35482,9053625,f2bc46b,f325a53,5ac9e73,e66ab12,1835f41]:Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.30.2Compare Source
🐞 Fixes
react-web-api/no-leaked-fetch: non-globalfetchcalls are no longer checked: a barefetch(...)whose name is bound by an enclosing scope (ex: a localfunction fetch() {}) and member calls on non-global objects (ex:api.fetch(...)) are ignored, whilewindow.fetch(...),globalThis.fetch(...), andself.fetch(...)are still recognized. (#2116, closes #2072)Full Changelog: Rel1cx/eslint-react@v5.30.1...v5.30.2
v5.30.1Compare Source
🐞 Fixes
react-x/no-duplicate-key: in.map()callbacks, all statically known keys are now treated as repeating, not only bare string literals.react-jsx/no-leaked-semicolon: same-line leaked semicolons after an expression container are now detected (ex:<div>{x};</div>,<div>{cond && <span />};</div>).🏗️ Internal
Full Changelog: Rel1cx/eslint-react@v5.30.0...v5.30.1
v5.30.0Compare Source
✨ New
@eslint-react/eslint-plugin: added theall-type-checkedpreset, which extendsallwith the rules that require type information. (#2095)@eslint-react/eslint-plugin: added the experimental@eslint-react/unstable-exhaustive-depsrule, forked fromexhaustive-deps, with ahooksoption modeled on Biome'suseExhaustiveDependencies(closureIndex/dependenciesIndexfor custom Hooks, andstableResultfor stable results). The rule lives in the unified plugin's ownsrc/ruleswhile incubating and is enabled in theallpreset (and thereby inall-type-checked). (#1698, #2078, #2095) Thanks to @dgesteves!react-x/set-state-in-effect: reworked around explicit effect roots, recursive value resolution, and a synchronous call graph. Stable aliases, multi-level helpers, named setups, IIFEs, anduseCallback/useMemo/useEffectEventwrappers now share one resolution path; indirect diagnostics point at the effect-side trigger and dedupe by setter sink; async functions remain deferred. (#2075)react-x/static-components: JSX member expression tags (ex:<Namespace.Bar />) are now analyzed. (#2114)🐞 Fixes
react-x/error-boundaries: optional-chainedcreateElementcalls are recognized as JSX-like return values. (#2084)react-x/no-direct-mutation-state: state assignments in nested constructor blocks (if, loops,try, and bare blocks) are no longer reported. (#2088)react-x/no-duplicate-key: only keys that provably have a duplicate are now reported. Unique siblings in a partially duplicate group (ex:[A, B, B]) are no longer reported, and duplicates followed by a unique key (ex:[A, A, B]) are now correctly reported; keys collected throughChildren.toArray()andChildren.map()are no longer reported; only elements returned by.map()callbacks are checked; literal keys are no longer overwritten by later keys; and.map()calls on array literals with at most one element are skipped. (#2108)react-x/no-duplicate-key: the fast-path text check now matches barekeyattributes and keys separated from=by whitespace (ex:<div key />,<div key = {id} />), so such elements are no longer silently skipped.react-x/no-missing-component-display-name:memocomponents passed to generic HOCs are recognized, so anonymous ones require a display name. (#2084)react-x/no-missing-context-display-name: the autofix now applies to exported contexts and no longer produces invalid syntax for multi-declarator declarations. (#2088, #2089)react-x/no-missing-key: elements with a spread attribute are no longer reported as missingkey, and TypeScript-wrapped iterator callbacks are unwrapped before checking. (#2086, #2088)react-x/no-nested-component-definitions: array pattern element defaults andmemopropsAreEqualcomparators are no longer reported as nested components; optional-chainedcreateElementreturns are recognized. (#2084)react-x/no-unstable-context-valueandreact-x/no-unstable-default-props: shadowedBoolean(),String(), andNumber()calls are no longer reported. (#2089)react-x/no-unused-class-component-members: statically resolvable computed member reads and destructuring are counted as usages. (#2088)react-x/refs: non-null guards whose terminating branch is atrystatement, an all-terminatingswitchwith adefaultclause, or an all-terminatingwhile (true)/for (;;)/do...whileloop are now recognized, so ref writes reached only when the ref is null are no longer reported. (#2093, #2109)react-x/set-state-in-effect: TypeScript-wrapped setups are resolved; zero-argument setters called directly in the setup are reported; timer or event callbacks nested inuseCallback/useEffectEventare no longer treated as synchronous setters; every possible setter is reported when the callee may resolve to more than one; the ref-derived exemption applies to any argument position of a custom state hook's setter; ref-derived early-return guards gate the following statements insidetry/switch/bare blocks and loop bodies or update clauses; ref provenance follows IIFEs; nested and outer effect setups are analyzed independently; and setter calls reached through the same effect-side trigger are reported once per setter name. (#2075, #2082, #2083)react-x/static-components: the render-boundary check now requires that at least one declaration of the component binding lives inside a render body, instead of only checking the first declaration. (#2110)react-x/static-components: static components wrapped byuseMemooruseCallback(ex:useMemo(() => External, [])) are no longer reported; the memoized value is traced instead of the hook call itself. (#2113, closes #1762) Thanks to @itisrmk!react-x/use-state: calls in computed object property keys and JSX subtrees are now detected by the lazy-initialization check. (#2080)react-jsx/no-children-prop-with-children:childrensupplied through a statically resolvable computed key in acreateElementprops object is now detected. (#2086)react-jsx/no-children-prop:childrensupplied through a statically resolvable computed key in acreateElementprops object is now detected, and the suggestion to movechildreninto element content is no longer offered when a following spread attribute could override it. (#2086, #2102)react-jsx/no-leaked-semicolon: leaked semicolons between a JSX child and its parent's closing tag on the same line are now detected. (#2102)react-jsx/no-useless-fragment: fragments with a spread attribute are no longer reported, and lone-CR whitespace, including&#​13;, is treated as formatting padding like LF and CRLF. (#2086, #2092)react-dom/no-dangerously-set-innerhtml-with-children: empty expression containers and comment-only children no longer count as children; lone-CR whitespace, including&#​13;, no longer counts either. (#2086, #2092)react-dom/no-hydrateandreact-dom/no-render: autofixes now skip calls with extra or spread arguments and calls whose return values are used, and no longer prepend the new import at the top of the file — existing imports are reused, duplicates are skipped, and new imports are placed after file-level directives, header comments, and existing imports. (#2103, #2104)react-dom/no-script-url: namespaced attributes such asxlink:hrefare now checked forjavascript:URLs. (#2086)react-dom/no-unsafe-iframe-sandbox:sandboxpermissions are matched as whole whitespace-separated tokens, fixing false positives likesandbox="not-allow-scripts". (#2112)react-dom/no-unsafe-target-blank: the suggestion for a missingrelattribute now inserts it after the last JSX attribute, so a spread attribute cannot override the suggested value. (#2086)react-dom/no-use-form-state: autofix-added imports now reuse existing imports, avoid duplicates, and follow file-level directives, header comments, and existing imports. (#2104)react-dom/no-void-elements-with-children: comment-only/empty containers, newline-only formatting whitespace, and lone-CR whitespace, including&#​13;, no longer count as children. (#2086, #2092)react-web-api/no-leaked-event-listener: dot access and static computed access (including simple template-literal keys) now match as the same property; optional-chained listeners, event types, and receivers pair with their cleanup; string-literal and template-literal option keys are recognized; cyclicsignalalias chains no longer recurse forever; and function-parameter callees are no longer mistaken for the enclosing function. (#2085, #2092, #2093, #2100)react-web-api/no-leaked-fetch:signaloption keys written as string literals or simple template literals are recognized. (#2093)react-web-api/no-leaked-intersection-observerandreact-web-api/no-leaked-resize-observer:observe(...)andunobserve(...)now pair on optional-chained elements. (#2093)react-debug/function-component: only the first argument ofmemo/forwardRefis treated as the wrapped component;propsAreEqualcomparators returning JSX are no longer reported, and functions in that position no longer inherit the surrounding binding or wrapper flags. Array pattern element defaults are no longer reported, and optional-chainedcreateElementreturns are recognized. (#2084)🪄 Improvements
Added fast-path text checks so rules skip AST traversal when their target term is absent from the file. (#2088)
Affected rules:
react-x/no-children-countreact-x/no-children-for-eachreact-x/no-children-mapreact-x/no-children-onlyreact-x/no-children-to-arrayreact-x/no-clone-elementreact-x/no-direct-mutation-statereact-x/no-implicit-childrenreact-x/no-implicit-keyreact-x/no-implicit-refreact-x/no-nested-lazy-component-declarationsreact-x/no-unused-class-component-membersJSX and
createElementrules no longer resolve spread props, since a spread's contents are unknown; only direct attributes and properties are inspected. (#2086)Affected rules:
react-x/no-missing-keyreact-jsx/no-children-propreact-jsx/no-children-prop-with-childrenreact-jsx/no-useless-fragmentreact-dom/no-dangerously-set-innerhtmlreact-dom/no-dangerously-set-innerhtml-with-childrenreact-dom/no-missing-button-typereact-dom/no-missing-iframe-sandboxreact-dom/no-string-style-propreact-dom/no-unsafe-iframe-sandboxreact-dom/no-unsafe-target-blankreact-dom/no-void-elements-with-childrenreact-x/no-unknown-property: attribute-tag, DOM-property, and standard-name lookups are cached per React version and resolved lazily. (#2086)react-x/set-state-in-effectandreact-x/set-state-in-render: setters are recognized only as the second element of auseStatearray destructuring; tuple-index access and object-pattern numeric keys are no longer detected. (#2075)📝 Documentation
eslint-plugin-react-jsx(#2102),eslint-plugin-react-dom(#2103),eslint-plugin-react-web-api, andeslint-plugin-react-x, and removed their next-step sections.react-jsx/no-comment-textnodes,react-jsx/no-key-after-spread, andreact-jsx/no-leaked-dollar. (#2102)noExplicitSpreadPropsrecipe to state that it provides no autofix. (#2089, #2107)🏗️ Internal
@eslint-react/ast,@eslint-react/core, and@local/testkit: added tests for AST tree types, core semantic interfaces, and type utilities.@eslint-react/ast: added theCollectandAnalyzenamespaces andTraverse.simpleTraverse;Analyze.isUnconditionallyTerminatingnow handlestrystatements, terminatingswitchstatements with adefaultclause, and terminatingwhile (true)/for (;;)/do...whileloops;Compare.isEqualnow comparesChainExpression, regex literals, and membercomputed/optionalflags;Collectnow traversesforinitializers and updates; renamedCheck.isConditionaltoCheck.isConditionalOrLoop; addedCheck.isArrayPatternElementDefault,Check.isObjectPatternElementDefault,Check.isLoopStatement, andExtract.getJSXName; improved private identifier handling; removed the general-purposeExtract.getMemberChain,Extract.getPropertyName,Extract.findProperty, andExtract.getAssignmentTargetshelpers in favor ofresolveAssignmentTargetsfrom@eslint-react/varand rule-local traversal. (#2080, #2083, #2084, #2086, #2092, #2093, #2099, #2100)@eslint-react/core: moved thecreateElementhelpers to@eslint-react/jsx; component detection now checks wrapper argument positions and unwraps chain expressions; improved render-method detection and qualified type names; narrowed the accepted node types of hook/component detection helpers. (#2075, #2077, #2084, #2099)@eslint-react/var: addedresolveOriginChain,isProvenanceEqual,hasDefault, andresolveAssignmentTargets; expandedresolveObjectTypeandcreateImportLookup, which now exposesisModuleBindinginstead ofhasNamespace; madeisValueEqualidentity-only (useisProvenanceEqualfor structural provenance); and removedresolveBindingTarget/BindingTarget, with binding targets now unwrapped inline. (#2085, #2086, #2088, #2100)@local/samples: hardened the sample rules. (#2107)@local/testkit: added averifyAndFixhelper for testing rules with autofixes. (#2078)eslintto10.14.0,typescript-eslintto8.72.1,nextto16.4.5,vitestto5.1.0,tsdownto0.23.7,nxto24.0.4,oxlintto1.91.0,viteto8.3.6,effectto4.1.2, and thefumadocspackages to16.18.0.react-x/static-componentsorigins; no behavioral changes.@typescript-eslint/typescript-estreedependency from@eslint-react/ast,@eslint-react/core,@eslint-react/var, andeslint-plugin-react-x. (#2080)inlinedDependenciesfield from the monorepo package configuration.New Contributors
Full Changelog: Rel1cx/eslint-react@v5.28.8...v5.30.0
v5.28.8Compare Source
🐞 Fixes
react-x/purity: builtin member resolution no longer follows computed or unknown middle segments (ex:window[fetch],window.myLibrary.fetch), preventing false reports of non-builtin calls. (#2074)🏗️ Internal
@eslint-react/eslint: added dual-purposegetTextfor direct or callback-style source text extraction, replacing repeatedcontext.sourceCode.getTextwrappers across packages. (#2073)Full Changelog: Rel1cx/eslint-react@v5.28.7...v5.28.8
v5.28.7Compare Source
🐞 Fixes
react-x/purity: now reportsDatecalls during render, includingDate(),Date(arg), andwindow.Date(); unlikenew Date(arg),Date(arg)ignores its arguments and always returns the current time. (#2071) Thanks to @aki05162525!🏗️ Internal
effectand@effect/platform-nodeto4.0.6,@tanstack/react-routerto1.170.46,@tanstack/react-startto1.169.4, andeslint-plugin-de-morganto2.3.0.New Contributors
Full Changelog: Rel1cx/eslint-react@v5.28.6...v5.28.7
v5.28.6Compare Source
🐞 Fixes
react-x/set-state-in-effect: the ref-derived parameter exemption now also applies to helpers wrapped inuseCallback(ex:measure(ref.current)wheremeasure = useCallback((el) => { setWidth(el.offsetWidth); }, [])). (#2065) Thanks to @amhunt!react-x/set-state-in-effect: a helper call behind a ref-derived guard (if, ternary, short-circuit, or early return) now exempts thesetStatecalls it reaches, as asetStatewritten in its place would be (ex:if (!anchorRef.current) return; commitPosition(0, true);); call sites are judged individually. (#2065) Thanks to @amhunt!New Contributors
Full Changelog: Rel1cx/eslint-react@v5.28.5...v5.28.6
v5.28.5Compare Source
✨ New
react-dom/no-unsafe-target-blank: the suggested fix now addsrel="noreferrer"instead ofrel="noreferrer noopener", sincenoreferreralready impliesnoopenerper the HTML spec; values combining both tokens remain valid. (#2068)🏗️ Internal
viteto8.3.5andlucide-reactto1.61.0.Full Changelog: Rel1cx/eslint-react@v5.28.4...v5.28.5
v5.28.4Compare Source
🐞 Fixes
Reverted the component-scope-bounded identifier resolution introduced in v5.28.3, including the per-component single-report attribution; class declarations in a component body remain recognized as per-render constructions. (#2062)
Affected rules:
react-x/no-unstable-context-valuereact-x/no-unstable-default-props📝 Documentation
🏗️ Internal
@eslint-react/var: removed theboundaryoption fromresolveandresolveObjectType, and theClassDeclarationresolution inresolveObjectType, following the revert. (#2062)Jsx-prefixed@eslint-react/coreexports to all-capsJSX(ex:JsxConfig→JSXConfig,isJsxLike→isJSXLike). (#2061)fumadocs-mdxto15.4.9.Full Changelog: Rel1cx/eslint-react@v5.28.3...v5.28.4
v5.28.3Compare Source
✨ New
Identifier resolution is now bounded by the enclosing component scope, so render-scoped values referenced from nested callbacks (ex:
items.map((item) => <Context.Provider value={foo}>)) are now detected, values declared outside the component (ex: module-level constants) are treated as stable, and nested components report each value only once, attributed to the innermost component. (#2060)Affected rules:
react-x/no-unstable-context-valuereact-x/no-unstable-default-propsClass declarations (ex:
class Foo {}in a component body) are now recognized as per-render constructions, so using one as a context value or default prop is now reported. (#2060)Affected rules:
react-x/no-unstable-context-valuereact-x/no-unstable-default-props🏗️ Internal
@eslint-react/var:resolveandresolveObjectTypenow accept aboundaryoption that bounds scope-chain traversal to an enclosing component or hook;resolveObjectTypealso resolvesClassDeclarationnodes. (#2060)typescript-eslintto8.72.0,fumadocs-coreandfumadocs-uito16.17.7,fumadocs-mdxto15.4.8,lucide-reactto1.60.0, andtypedoc-plugin-markdownto4.14.1.Full Changelog: Rel1cx/eslint-react@v5.28.2...v5.28.3
v5.28.2Compare Source
🐞 Fixes
:sequence in the YAML frontmatter description of thereact-x/use-memodoc; the rule scaffold script now emits a YAML-safe quoted description so scaffolded rules cannot reintroduce the issue.📝 Documentation
react-debug/jsxrule doc messages with the actual JSON report format.10.0.0in the READMEs and getting-started guides.isAPI/isAPICalldocs and updated the custom rule samples to useis.APICall. (#2059)🏗️ Internal
react-ximmutability rule modules (collect,effects,helpers,origins). (#2056)postcssoverride to8.5.31.Full Changelog: Rel1cx/eslint-react@v5.28.1...v5.28.2
v5.28.1Compare Source
🐞 Fixes
react-dom/no-unknown-property: fixed a false positive where the React camelCase SVG proprenderingIntentwas reported as an unknown property, including on code produced by this rule's own autofix forrendering-intent. (#2055)react-jsx/no-useless-fragment: the auto-fixer no longer unwraps fragments outside JSX whose children are all whitespace (ex:const x = <> </>;orreturn <>\n</>withallowExpressions: false); the previous fix produced syntactically invalid JavaScript such asconst x = ;. These fragments are still reported, just without a fix. (#2055)📝 Documentation
🏗️ Internal
eslintto10.13.0,pnpmto12.14.0,tsl-dxto0.15.0,@effect/language-serviceto0.87.5, andlucide-reactto1.59.0.Full Changelog: Rel1cx/eslint-react@v5.28.0...v5.28.1
v5.28.0Compare Source
✨ New
@eslint-react/eslint-plugin: the general-purpose presets now enable JSX syntax support vialanguageOptions.parserOptions.ecmaFeatures.jsx: true, so you no longer need to configure it yourself. (#2049)Affected presets:
recommendedrecommended-typescriptrecommended-type-checkedstrictstrict-typescriptstrict-type-checked🏗️ Internal
fumadocs-coreandfumadocs-uito16.17.5, andlucide-reactto1.58.0.Full Changelog: Rel1cx/eslint-react@v5.27.4...v5.28.0
v5.27.4Compare Source
🐞 Fixes
@eslint-react/jsx:resolveAttributeValuenow handles a parser-toleratedJSXFragmentin attribute value position (ex:<a href=<></> />), reporting it as kind"element"instead of falling through toundefined; as a result,react-dom/no-missing-iframe-sandboxnow reports<iframe sandbox=<></> />instead of silently skipping it. (#2048)Full Changelog: <https://github.com/Rel1cx/eslint-r
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.