fix(deps): update misc npm packages - #2302
Merged
Merged
Conversation
✅ Deploy Preview for cert-manager ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
September 26, 2026 09:04
ee1821c to
1cbca68
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
September 26, 2026 16:30
1cbca68 to
520867f
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
September 26, 2026 20:30
520867f to
5586a78
Compare
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: erikgb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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:
5.20.5→5.20.816.3.5→16.3.616.3.5→16.3.616.3.5→16.3.63.9.8→3.9.9Release Notes
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.20.8🐞 Fixes
@eslint-react/core:isJsxLikenow recognizes JSX wrapped in TypeScript expressions (as,satisfies, type assertions, and non-null assertions) andawaitexpressions.@eslint-react/jsx:isFragmentElementnow requires the configuredjsxFragmentFactory, avoiding an implicit React fragment factory for custom JSX runtimes.🏗️ Internal
@eslint-react/jsx: exported theAttributeValuetype from the package entry point.@eslint-react/var: renamed theAssignmentTargettype toEnclosingAssignmentTargetand inlinedgetRequireExpressionArgumentsinto its sole consumer.Full Changelog: Rel1cx/eslint-react@v5.20.6...v5.20.8
v5.20.6Compare Source
🐞 Fixes
react-x/globals:for...in/for...ofloop targets without a declaration (e.g.for (globalValue of items)) are now collected as writes instead of being missed.react-x/immutability: destructuring assignment targets (e.g.({ a: props.x } = value)) andfor...in/for...ofloop targets without a declaration are now collected as mutations instead of being missed.react-x/purity: builtin alias resolution now preserves the property path, so aliases of impure builtins (const random = Math.random; random(),const { now } = Date; now(),window.Math.random()) are now detected instead of being missed; unknown-global roots are not followed, preventing speculative reports.react-x/refs: destructuring assignments, for-in/of loop targets, anddeleteoperations onref.currentare now classified as writes instead of being misreported as reads.react-x/refs: refs passed to constructor calls (new Widget(ref)) and tagged templates are now checked for render-time exposure, same as refs passed to plain functions.react-x/refs: themergeRefsexemption for passing refs now survives simple variable aliases (const combine = mergeRefs), resolved position-aware so reassigned aliases lose it again.react-x/use-memo: reassignments of outer variables through destructuring patterns andfor...in/for...ofloop targets insideuseMemocallbacks are now reported instead of being missed; property mutation targets remain exempt, matching the React Compiler'sStoreContextsemantics.🏗️ Internal
@eslint-react/var: splitresolveinto a value-basedresolveand a new origin-basedresolveOrigin, and updated the consumers inreact-web-apiandreact-xrules accordingly. (#1964)fumadocsto16.15.12,fumadocs-mdxto15.4.3,tsl-dxto0.13.6,eslint-plugin-de-morganto2.2.0, andeslint-plugin-regexpto3.3.1.Full Changelog: Rel1cx/eslint-react@v5.20.5...v5.20.6
vercel/next.js (@next/eslint-plugin-next)
v16.3.6Compare Source
This release contains a security fix for GHSA-vcvr-r3jv-pc5j: Remote Code Execution in next/og ImageResponse
vercel/next.js (next)
v16.3.6Compare Source
prettier/prettier (prettier)
v3.9.9Compare Source
diff
Markdown: Fix text with
$been incorrectly parsed as math syntax (#20140 by @fisker)Configuration
📅 Schedule: (in timezone Europe/London)
🚦 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.