Update dependency @eslint-react/eslint-plugin to v5.9.0#1054
Update dependency @eslint-react/eslint-plugin to v5.9.0#1054renovate[bot] wants to merge 1 commit into
Conversation
772a12c to
4891c1e
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate Clean patch bump — upstream 5.8.1 is docs and scaffolding only, no rule behavior changes. CI is green. LGTM.
4891c1e to
28f4242
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate Same story as 5.8.1 — 5.8.2 upstream is docs + internal only, no rule behavior changes. Lockfile diff is restricted to @eslint-react/* and the corresponding eslint-plugin-react-* peers. CI is green. LGTM.
28f4242 to
b305846
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate Patch bump from 5.8.2 → 5.8.3. Upstream 5.8.3 is a targeted false-positive fix in react-dom/no-unknown-property (adds React 19 precedence/blocking to the known-attribute allowlist, with version-gated tag checks). Lockfile diff is restricted to @eslint-react/* and the matching eslint-plugin-react-* peers — no unrelated transitive shuffling. Build checks are green. LGTM.
b305846 to
f8efc86
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate Straightforward patch bump and the lockfile diff checks out. Holding off on approval this round though — CI is red and won't self-heal: pnpm install --frozen-lockfile is blocked by pnpm's minimumReleaseAge (5.8.4 was published today, clears ~tomorrow), and hiding behind that the committed client SBOM is stale and needs regenerating. Details inline.
| }, | ||
| "devDependencies": { | ||
| "@eslint-react/eslint-plugin": "5.8.3", | ||
| "@eslint-react/eslint-plugin": "5.8.4", |
There was a problem hiding this comment.
@renovate [medium] The 5.8.4 bump itself is clean — upstream is docs + internal-only (optional-chaining cleanup in rules, added null-safety tests), no rule behavior changes, and the lockfile diff is consistent (@eslint-react/* → 5.8.4 plus the transitive @typescript-eslint 8.59.3→8.59.4 consolidation). But CI is red and won't go green on its own. Two things: pnpm install --frozen-lockfile fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION because 5.8.4 was published today (clears once it ages past pnpm's ~1-day cutoff, roughly tomorrow), and the committed client SBOM is stale — client/sbom/.lock-hash no longer matches sha256(pnpm-lock.yaml + package.json). The refresh_sbom workflow already failed twice on this commit (it hits the same age gate), so it won't self-heal. Once the packages age out, regenerate the SBOM and commit it.
🤖 Prompt for AI agents
In the client/ directory, the committed SBOM is stale after bumping @eslint-react/eslint-plugin to 5.8.4: client/sbom/.lock-hash does not match the sha256 of pnpm-lock.yaml + package.json. After the @eslint-react/* 5.8.4 packages have aged past pnpm's minimumReleaseAge cutoff (~2026-05-23), run pnpm run sbom:force in client/ and commit the regenerated client/sbom/bom.json and client/sbom/.lock-hash.
There was a problem hiding this comment.
@renovate Status update after the rebase onto develop: the minimumReleaseAge block has cleared, so pnpm install --frozen-lockfile passes now and the only thing still red is the SBOM gate. client/sbom/ is stale — .lock-hash is bf47dc0… but pnpm-lock.yaml + package.json now hash to 396bc75…, so run-tests / build fails with "client/sbom/ is stale". It still needs pnpm run sbom:force run in client/ and the regenerated bom.json + .lock-hash committed.
Heads up for the maintainers: this won't self-heal. The refresh_sbom workflow is now failing right at the start with "Neither SBOM_BOT_APP_ID/SBOM_BOT_PRIVATE_KEY nor SBOM_BOT_PAT is configured" — so the auto-refresh bot can't push the SBOM until those repo secrets are wired up. Until then someone has to regenerate and push it manually. Leaving this unresolved until the SBOM lands.
There was a problem hiding this comment.
@renovate Now bumped to 5.8.5 — the bump itself is still clean. CI is red for the same SBOM reason plus a fresh wrinkle: client/sbom/ is still stale (.lock-hash is bf47dc0… but pnpm-lock.yaml + package.json now hash to 8cb8709…), and because 5.8.5 was published today the minimumReleaseAge gate is back, so pnpm install --frozen-lockfile fails again in build-client/e2e (clears in ~1 day). Once the packages age out, someone still needs to run pnpm run sbom:force in client/ and commit the regenerated bom.json + .lock-hash — the refresh_sbom bot can't do it (SBOM_BOT secrets still unconfigured). Leaving unresolved.
There was a problem hiding this comment.
@renovate Still unresolved on 5.8.6. pnpm install --frozen-lockfile is failing again because the 5.8.6 @eslint-react/eslint-plugin package set was published today and is inside pnpm minimumReleaseAge, and client/sbom/ is still stale (.lock-hash is bf47dc0..., current hash is 055c58f...). Once the age gate clears, run pnpm run sbom:force in client/ and commit the regenerated SBOM files; the refresh workflow still cannot push this automatically because SBOM_BOT credentials are not configured.
There was a problem hiding this comment.
@renovate Still unresolved on 5.8.7. The client jobs are failing again on pnpm minimumReleaseAge for the newly published 5.8.7 @eslint-react package set, and client/sbom/ is still stale: .lock-hash is bf47dc0..., while the current pnpm-lock.yaml + package.json hash is e9b6e94.... Once the age gate clears, run pnpm run sbom:force in client/ and commit the regenerated SBOM files; the refresh workflow still cannot push this automatically because the SBOM bot credentials are missing.
There was a problem hiding this comment.
@renovate Still unresolved on 5.8.12. CI is red on the fresh pnpm minimumReleaseAge block for the 5.8.12 @eslint-react package set, and client/sbom/ is still stale: .lock-hash is bf47dc04..., while the current pnpm-lock.yaml + package.json hash is 93894c5a.... Once the age gate clears (latest package publish time is 2026-06-04 21:02:59 UTC, so roughly after 2026-06-05 21:03 UTC), run pnpm run sbom:force in client/ and commit the regenerated SBOM files; the refresh workflow still cannot push this automatically because the SBOM bot credentials are missing.
There was a problem hiding this comment.
@renovate Still open on 5.8.13. CI is red on the fresh pnpm minimumReleaseAge block for the 5.8.13 package set, and client/sbom/.lock-hash is still bf47dc04... while the current hash is cdd48297...; once the age gate clears, run pnpm run sbom:force in client/ and commit the regenerated SBOM files.
There was a problem hiding this comment.
@renovate Still unresolved on 5.8.16. CI is failing on pnpm minimumReleaseAge for the newly published 5.8.16 package set, and client/sbom/.lock-hash is still bf47dc04... while the current package/lockfile hash is 4b15467c...; once the age gate clears, regenerate and commit client/sbom/. The refresh workflow still cannot push this automatically because the SBOM bot credentials are missing.
There was a problem hiding this comment.
@renovate Still unresolved on 5.8.17. client/sbom/.lock-hash is still bf47dc04..., but the current pnpm-lock.yaml + package.json hash is bd674768..., so client/sbom/ still needs regeneration and a commit. The last CI run also hit pnpm minimumReleaseAge because the 5.8.17 packages had just been published; that should clear on rerun, but the SBOM mismatch will remain until pnpm run sbom:force is committed.
There was a problem hiding this comment.
@renovate Still open on 5.9.0. The committed client/sbom/.lock-hash is still bf47dc04..., while the current pnpm-lock.yaml + package.json hash is 8f76b0be...; client/sbom/ still needs pnpm run sbom:force and a commit. CI is also currently hitting pnpm minimumReleaseAge for the freshly published 5.9.0 package set, so rerun after the age gate clears, but the SBOM mismatch will remain until the regenerated files are committed.
f293297 to
875e2f3
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The bump itself is still clean and the rebase fixed the install block (minimumReleaseAge has cleared). But CI's SBOM gate is still red — client/sbom/ wasn't regenerated after the lockfile change, so run-tests / build fails with "client/sbom/ is stale". Needs pnpm run sbom:force run in client/ and the result committed (details in the thread). Holding off on approval until that lands and the build goes green.
875e2f3 to
9f93ef8
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate Clean bump to 5.8.5 (upstream is docs + internal-only, no rule behavior changes), but holding off again because CI is red. The minimumReleaseAge gate is back now that 5.8.5 published today, so pnpm install --frozen-lockfile fails in build-client/e2e (self-heals in ~a day), and the committed client/sbom/ is still stale — it needs a manual pnpm run sbom:force + commit since the refresh_sbom bot can't push it (SBOM_BOT secrets unconfigured). Details in the thread above.
9f93ef8 to
f1b7400
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks straightforward, but the requested CI/SBOM fix is not addressed on the 5.8.6 update. The client jobs are blocked by pnpm minimumReleaseAge for the newly published 5.8.6 packages, and client/sbom/ is still stale, so I need to keep this as changes requested.
f1b7400 to
7028b55
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks straightforward, but the requested CI/SBOM fix is still open on 5.8.7. Client install is blocked by pnpm minimumReleaseAge again, and the committed client SBOM hash is stale; I updated the existing thread with the current hashes and log details.
7028b55 to
b13c08c
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The bump itself still looks straightforward, but the requested SBOM fix is still missing and CI is red again on the 5.8.8 age gate. Keeping changes requested until client/sbom/ is regenerated and committed once the packages age out.
b13c08c to
2a0b649
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself is still straightforward, but the requested CI/SBOM fix is still open on 5.8.9. CI is red on pnpm minimumReleaseAge for the freshly published packages, and client/sbom/ still needs regeneration once the age gate clears.
2a0b649 to
f428c64
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks straightforward, but the requested SBOM fix is still missing. client/sbom/.lock-hash does not match the current package/lockfile hash, and the refresh workflow cannot push the regeneration, so CI remains red. Keeping changes requested until the SBOM files are regenerated and committed.
f428c64 to
eb92d38
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The bump itself still looks straightforward, but the requested SBOM/CI fix is still open on 5.8.11. CI is red on the fresh pnpm minimumReleaseAge block, and client/sbom/ still needs regeneration once that clears.
eb92d38 to
c3c8ec4
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump still looks straightforward, but the requested CI/SBOM fix is still open on 5.8.12. Client CI is blocked by pnpm minimumReleaseAge for the freshly published packages, and client/sbom/ still needs regeneration once the age gate clears.
c3c8ec4 to
87037b1
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks straightforward, but CI is red and the previous SBOM request is still open. The current 5.8.13 packages are inside pnpm minimumReleaseAge, and client/sbom/.lock-hash still needs to be regenerated from the current package/lockfile once that clears.
87037b1 to
ffd54d7
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks straightforward, but the previous CI/SBOM blocker is still open. client/sbom/ was not regenerated for the current package/lockfile, and the fresh 5.8.16 packages are still inside pnpm minimumReleaseAge, so I need to keep this as changes requested.
ffd54d7 to
df0b856
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The dependency bump itself still looks fine, but the previous SBOM/CI blocker is still open. The committed client/sbom/.lock-hash is stale for the current package/lockfile pair, and the refresh workflow still cannot push the regenerated SBOM automatically. Keeping changes requested until client/sbom/ is regenerated and committed.
df0b856 to
f5ed1ad
Compare
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@renovate The 5.9.0 bump itself still looks straightforward, but the previously requested SBOM/CI fix is still open. client/sbom/.lock-hash is stale for the current package/lockfile, and client CI is currently also blocked by pnpm minimumReleaseAge for the freshly published 5.9.0 packages. Keeping changes requested until client/sbom/ is regenerated and committed and CI can pass.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
5.8.3→5.9.0Release Notes
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.9.0Compare Source
✨ New
react-web-api/no-leaked-intersection-observerrule to prevent leakedIntersectionObserverinstances in components and hooks, enabled aswarnin therecommendedpreset (#1841, #1868).🐞 Fixes
react-web-api/no-leaked-intersection-observer,react-web-api/no-leaked-resize-observer: Report whendisconnectis only called inside the observer's own callback, since the callback may never run if the component unmounts before the element intersects or resizes (#1872).🏗️ Internal
SECURITY.mddocumentation (#1871).fumadocs-coreandfumadocs-uito16.10.1.New Contributors
Full Changelog: Rel1cx/eslint-react@v5.8.19...v5.9.0
v5.8.19Compare Source
🏗️ Internal
isJsxLikein core package and added behavior boundary tests (#1869).@types/nodeto^25.9.3.Full Changelog: Rel1cx/eslint-react@v5.8.18...v5.8.19
v5.8.18Compare Source
🐞 Fixes
react-x/no-array-index-keyandreact-x/no-missing-keyrules (#1867).📝 Documentation
🏗️ Internal
postinstallscript on the website.textlintrules for inclusive language.eslintpeer dependency.Full Changelog: Rel1cx/eslint-react@v5.8.17...v5.8.18
v5.8.17Compare Source
📝 Documentation
🏗️ Internal
typescript-eslintpackages tov8.61.0(#1863, #1864).rename-rulescript and npm script (#1857).sponsors.svg(#1855).undiciand cleaned updprintconfig (#1854).Full Changelog: Rel1cx/eslint-react@v5.8.16...v5.8.17
v5.8.16Compare Source
🐞 Fixes
Full Changelog: Rel1cx/eslint-react@v5.8.15...v5.8.16
v5.8.15📝 Documentation
AGENTS.mdandCONTRIBUTING.mddocuments and references (#1848).🏗️ Internal
@types/*dependencies (#1852).Full Changelog: Rel1cx/eslint-react@v5.8.13...v5.8.15
v5.8.13Compare Source
📝 Documentation
GoogleCloudPlatform/gke-mcpand removed archivedantfu/shiki-streamfrom community projects on the website.no-multiple-children-in-titlerecipe from the website.🏗️ Internal
RuleListenerreturn type to all rulecreatefunctions (#1845).react-domrules, JSX rules, andnaming-conventionrules (context-name,id-name,ref-name).react-x/no-leaked-conditional-rendering(#1844).pnpmand updated lockfile.tsdownto0.22.2and updated dependencies.merge()calls in rules (#1843).ubuntu-latest.Full Changelog: Rel1cx/eslint-react@v5.8.12...v5.8.13
v5.8.12Compare Source
🪄 Improvements
jsx: AlignedgetChildrenwith Babel'sbuildChildrenandcleanJSXElementLiteralChildpatterns, improving whitespace handling accuracy inreact-jsx/no-useless-fragmentandreact-jsx/no-children-proprules. Migrated child text cleanup to@eslint-react/jsxutilities and removed locallib.tshelpers. (#1836)jsx: RemovedisPaddingWhitespaceAPI and added whitespace boundary tests forreact-jsx/no-useless-fragmentandreact-dom/no-dangerously-set-innerhtml-with-childrenrules. (#1837)jsx: RenamedcleanJSXTextValuetocollapseMultilineTextin the public API and updatedreact-jsx/no-useless-fragmentto use the new name. (#1838)📝 Documentation
🏗️ Internal
scripts/generate-website-icons.pyfor automated icon generation and refined logo geometry across all website assets. (#1833)import-integrity-lintandenhanced-resolve.axiosto^1.17.0andshikito4.2.0.dompurifyandrolldown.no-useless-fragment,no-children-prop, andno-dangerously-set-innerhtml-with-children. (#1836, #1837, #1838)Full Changelog: Rel1cx/eslint-react@v5.8.11...v5.8.12
v5.8.11Compare Source
📝 Documentation
🏗️ Internal
19.2.7(#1827).@fontsource/iosevka-aileand switched to system font fallbacks.6.0.3(#1828).@typescript-eslint/*to8.60.1,react/react-domto19.2.7,nextto16.2.7, and@types/reactto19.2.16.Full Changelog: Rel1cx/eslint-react@v5.8.10...v5.8.11
v5.8.10Compare Source
🐞 Fixes
react-dom/no-unused-class-component-members: Aligned preset details in rule documentation (#1825).react-dom/no-unsafe-iframe-sandbox,react-x/context-name,react-x/id-name,react-x/ref-name,react-x/no-unnecessary-use-prefix,react-x/no-string-style-prop: Fixed missing or incorrect presets in rule documentation (#1826).📝 Documentation
naming-convention: Expanded examples and annotated Ok cases forcontext-name,id-name, andref-namerules (#1819).MyComponentexamples toButtoncomponent in custom rules of props and function component definition recipes (#1823).azat-ioeslint-config to the community presets list.🏗️ Internal
jsx: Consolidated whitespace child predicates and addedisEmptyStringExpressionto the public API (#1820).verify-docs.ts(#1822).AGENTS.mdguide for AI coding agents (#1824)..pkgs/*.viteto^8.0.15andansisto^4.3.1across workspace packages.New Contributors
Full Changelog: Rel1cx/eslint-react@v5.8.9...v5.8.10
v5.8.9Compare Source
🐞 Fixes
react-x/no-direct-mutation-state: Detect nested state mutations and member expressions in assignment expressions (#1818).📝 Documentation
🏗️ Internal
.vscodedirectories from all examples, added missingengines.nodeto Preact examples, cleaned up redundant.config/*.tsfromtsconfig.node.json, and updated.gitignore.eslint,tinyglobby, andtsdownacross workspace packages; added@fontsource/iosevka-aileto the website; reordered CSS imports inlayout.tsx..sentruxbaseline timestamp.Full Changelog: Rel1cx/eslint-react@v5.8.8...v5.8.9
v5.8.8Compare Source
📝 Documentation
kit: Addedis.APICallcallout to the Kit documentation (#1813).jsx: UpdatedgetChildrenandhasChildrenAPI documentation to reflect empty string children behavior.custom-rules-of-childrenrecipe and cross-linked the remaining recipes.🏗️ Internal
react-x/no-misused-capture-owner-stack: Added edge-case tests forcaptureOwnerStack(#1813).data-themeattribute.tsdownversion in@local/configs.trustPolicy: "no-downgrade"and addedminimumReleaseAge: 1440(1 day).eslintto10.4.1across workspace packages.pnpmto11.5.0and refreshed the lockfile.fumadocspackages andtinyexec.eslint-plugin-package-jsonto1.2.0..gitignore.Full Changelog: Rel1cx/eslint-react@v5.8.7...v5.8.8
v5.8.7Compare Source
🐞 Fixes
react-x/no-create-ref: Fixed a false positive wherecreateRefcalls in non-React classes were reported. The rule now only reportscreateRefcalls inside function components or Hooks (#1812).react-x/no-unused-state: Removed the "only used in effects" detection so the rule only reports state variables that are defined but never used, reducing false positives (#1808, #1749).jsx: Aligned children filtering andhasChildrenbehavior with React source, updatingno-children-propandno-useless-fragmentrules accordingly (#1805).zodpeer dependency to support both v3 and v4 (#1810).📝 Documentation
react-dom,react-web-api,react-x: Enriched rule MDX examples with TypeScript snippets from react.dev (#1809).react-dom: Added more rule examples tono-dangerously-set-innerhtml,no-find-dom-node,no-hydrate,no-render, andno-render-return-valuedocumentation (#1804).react-dom: Added legitimateflushSyncuse cases tono-flush-syncrule documentation (#1803).10.3.0.offpreset disables all rules.offpreset description in README.🏗️ Internal
react-x/no-misused-capture-owner-stack: Refactored theprocess.env.NODE_ENVdetection helpers to use the sharedcore.isAPIutility (#1812).react-x/no-unused-state: Removed incorrect invalid test cases.jsx: Added targeted test cases for empty string children behavior inno-children-prop-with-childrenandno-useless-fragmentrules (#1806).wwwprefix fromeslint-react.xyzlinks (#1807).eslint-plugin-functionand bumped website dependencies (#1811).scripts/libinto thescriptsroot..textlintrc.json.enriching-rule-examples-from-react-dev.mdfrom main branch.no-useless-fragment,no-children-prop, andno-children-prop-with-children(#1805).@takumi-rs/image-responseto^1.6.0dompurifyto3.4.6fumadocs-mdxand updated pnpm lockfiletsdownto0.22.1g-plane/markup_fmtandmarkdown)Full Changelog: Rel1cx/eslint-react@v5.8.6...v5.8.7
v5.8.6Compare Source
📝 Documentation
react-x/context-namerule description accuracy.react-x,react-dom, andreact-web-apirule documentation.term-based-rule-patterns.mddocumentation.🏗️ Internal
ast: ReplacedisLiteralwithisStringLiteralinCheckutilities (#1798).tsdownandtslbase configs to factory functions.@local/samplespackage (#1800).@typescript-eslintto^8.60.0eslint-plugin-jsdocto63.0.0fumadocspatch versionsnxto^22.7.4pnpmand lockfile updatesFull Changelog: Rel1cx/eslint-react@v5.8.5...v5.8.6
v5.8.5Compare Source
📝 Documentation
docs/rule-implementation-patterns.md) and term-based rule patterns guide (docs/term-based-rule-patterns.md).5.1.0to5.0.0across README and documentation..textlintrc.jsonpatterns.🏗️ Internal
@effect/language-serviceto^0.86.2@takumi-rs/image-responseto^1.3.0@tsconfig/vite-reactto^8.0.6@types/nodeto^25.9.1@types/reactto^19.2.15eslint-plugin-package-jsonto^1.1.0fumadocs-coreto^16.9.0fumadocs-mdxto^15.0.7fumadocs-uito^16.9.0lru-cacheto11.5.0nxto^22.7.3postcssto^8.5.15viteto^8.0.14vitestto^4.1.7pnpmto11.2.1Full Changelog: Rel1cx/eslint-react@v5.8.4...v5.8.5
v5.8.4Compare Source
📝 Documentation
Hintpopover with a direct link to the FAQ anchor explaining the project's human/LLM collaboration policy.isClassComponentandJsxConfig.🏗️ Internal
core: SimplifiedisClassComponentby removing thecontextparameter and replacingisClassComponentLoosewith the simplified function.eslint-plugin-react-x: Removed unnecessary optional chaining across multiple rules (immutability,no-unused-state,purity,refs,set-state-in-effect,static-components,use-memo, etc.) and expanded test coverage for edge cases (#1792).actions/setup-nodecache parameter error.@takumi-rs/image-responseto 1.2.1,fumadocs-mdxto 15.0.6,import-integrity-lintto 1.1.1,preactto 10.29.2,tsxto 4.22.1,@typescript-eslintto^8.59.4,@types/nodeto^25.9.0,dompurifyto^3.4.5,pnpmto11.1.3,textlintto 15.7.1, and dprint TypeScript plugin to 0.96.1.tsl.config.ts.pnpm-workspace.yamlfrom^6.0.3to5.9.3..github/zizmor.yml.scripts/verify-lockfile.ts,scripts/verify-devtools.ts, and all references to them.react-jsx/no-children-prop(no logic change).Full Changelog: Rel1cx/eslint-react@v5.8.3...v5.8.4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.