Repository navigation
fix(deps): update patch updates (patch) - #1234
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
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
October 20, 2026 12:32
679ed1a to
22982f8
Compare
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
October 22, 2026 08:23
22982f8 to
0c87178
Compare
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
3 times, most recently
from
October 23, 2026 13:50
0787abf to
ce34b2f
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
October 26, 2026 09:47
ce34b2f to
9b987ea
Compare
Signed-off-by: Renovate Bot <bot@renovateapp.com>
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
October 26, 2026 17:50
9b987ea to
19679ec
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:
4.4.24→4.4.2510.0.3→10.0.45.28.2→5.28.81.6.27→1.6.28>=4.29.3→>=4.29.41.0.30001817→1.0.30001819^10.2.0→^10.2.1^4.2.2→^4.2.3](https://renovatebot.com/diffs/npm/fast-uri@>=3.0.0 <3.1.3/4.2.2/4.2.3)^4.2.2→^4.2.3](https://renovatebot.com/diffs/npm/fast-uri@>=4.0.0 <4.1.5/4.2.2/4.2.3)7.0.2004→7.0.2005>=8.12.2→>=8.12.3bump,lockfileUpdate, orrollbackupdates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).Release Notes
anolilab/semantic-release (@anolilab/multi-semantic-release)
v4.4.25Compare Source
Dependencies
anolilab/javascript-style-guide (@anolilab/prettier-config)
v10.0.4Compare Source
Dependencies
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
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
browserslist/browserslist (browserslist@<=4.28.6)
v4.29.4Compare Source
browserslist/caniuse-lite (caniuse-lite)
v1.0.30001819Compare Source
v1.0.30001818Compare Source
sindresorhus/execa (execa)
v10.2.1Compare Source
exactOptionalPropertyTypes2b6988bfastify/fast-uri (fast-uri@>=3.0.0 <3.1.3)
v4.2.3Compare Source
Security
This security release fixes four URI parsing and normalization vulnerabilities in fast-uri 4.x. Applications that process untrusted URI input should upgrade to v4.2.3.
Upgrade with:
Thanks to @zekth for reporting the scheme, host, and relative-reference issues, and to @UlisesGascon for finding the suffix-reference issue and reviewing the remediations.
What's Changed
Full Changelog: fastify/fast-uri@v4.2.2...v4.2.3
nodejs/undici (undici@<8.10.2)
v8.12.3Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.12.2...v8.12.3
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.