Repository navigation
Update npm dependencies - #912
Merged
Merged
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
✅ Deploy Preview for ucmacm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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:
5.104.4→5.104.55.104.4→5.104.54.9.1→4.10.01.88.0→1.89.05.12.1→5.13.05.28.1→5.28.55.28.65.28.1→5.28.55.28.65.28.1→5.28.55.28.65.28.1→5.28.55.28.61.59.0→1.61.024.22.0→24.22.1^0.154.0→^0.155.0^0.73.0→^0.74.01.88.0→1.89.012.14.0→12.15.08.71.2→8.72.08.3.4→8.3.5Release Notes
TanStack/query (@tanstack/eslint-plugin-query)
v5.104.5Compare Source
No changes in this release.
TanStack/query (@tanstack/react-query)
v5.104.5Compare Source
Patch Changes
1f8d134- RecomputeuseMutationStateanduseIsMutatingresults when their filters, selector, or query client change, without waiting for a mutation cache update.f608f93]:schoero/eslint-plugin-better-tailwindcss (eslint-plugin-better-tailwindcss)
v4.10.0Compare Source
compare changes
Features
Fixes
Documentation
Chore
❤️ Contributors
oxc-project/eslint-plugin-oxlint (eslint-plugin-oxlint)
v1.89.0Compare Source
What's Changed
extendsentry win, matching oxlint by @Sysix with @Claude in #803allowanddenyseverities from the oxlint config by @RaphaelFakhri in #806New Contributors
Full Changelog: oxc-project/eslint-plugin-oxlint@v1.88.0...v1.89.0
azat-io/eslint-plugin-perfectionist (eslint-plugin-perfectionist)
v5.13.0Compare Source
compare changes
🚀 Features
(4d542f6)
🏎 Performance Improvements
(0f3cda2)
(8b7f6d1)
(4d06954)
🐞 Bug Fixes
(8292ce8)
(2e94623)
(a93611b)
(8a8f4f3)
(7951342)
(f1665c1)
(8c713e1)
❤️ Contributors
Rel1cx/eslint-react (eslint-plugin-react-dom)
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
lucide-icons/lucide (lucide-react)
v1.61.0: Version 1.61.0Compare Source
What's Changed
circle-chevrons-down,circle-chevrons-left,circle-chevrons-rightand 1 more icons by @ypotti in #5025New Contributors
Full Changelog: lucide-icons/lucide@1.60.0...1.61.0
v1.60.0: Version 1.60.0Compare Source
What's Changed
tombstoneicon by @ryck in #4929smartphone-user-roundicon by @hitanshu-machhi in #4586baconicon by @devkamani9313-lab in #4694letter-spacingicon by @madebyoz in #3038line-heighticon by @madebyoz in #3039brain-officon by @ej52 in #3535graph-hubicon by @Carlito-la-banane in #4974New Contributors
Full Changelog: lucide-icons/lucide@1.59.0...1.60.0
nodejs/node (node)
v24.22.1: 2026-10-21, Version 24.22.1 'Krypton' (LTS), @aduh95Compare Source
This is a security release.
Notable Changes
BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH(Antoine du Hamel)0ed4268(Evgenii Kliuchnikov)Commits
2a73ee5a89] - crypto: update root certificates to NSS 3.131.1 (Antoine du Hamel) #668774d6990b33c] - crypto: reset random caches across snapshots (Filip Skokan) nodejs-private/node-private#9874b3c9bbf9f] - crypto: harden X.509 conversion and formatting (Filip Skokan) nodejs-private/node-private#10079243b105b6] - crypto: update root certificates to NSS 3.129 (Node.js GitHub Bot) #664961e39cd53c7] - deps: update c-ares to 1.34.9 (Node.js GitHub Bot) #6686849dff6f57a] - deps: brotli: cherry-pick0ed4268(Evgenii Kliuchnikov) nodejs-private/node-private#1002fca511adc5] - deps: V8: backport93cd21e(Joyee Cheung) nodejs-private/node-private#100818711c7567] - deps: update timezone to 2026e (Node.js GitHub Bot) #66419fa77cfb1ad] - deps: update timezone to 2026d (Node.js GitHub Bot) #66333b84f9f186b] - deps: update archs files for openssl-3.5.9 (Node.js GitHub Bot) #66396ff0664c3ba] - deps: upgrade openssl sources to openssl-3.5.9 (Node.js GitHub Bot) #663961d4c89ef87] - deps: update undici to 7.30.1 (Node.js GitHub Bot) #66764843a1627dc] - dns: validate resolve inputs for null bytes (James M Snell) nodejs-private/node-private#98496c3ccb1fc] - http: ensure agent data guard works without I/O (James M Snell) nodejs-private/node-private#9838dc18a6218] - permission: check permission model in realpathSync (RafaelGSS) nodejs-private/node-private#973b5f41529df] - src: exposeBROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH(Antoine du Hamel) nodejs-private/node-private#100201acf0ee74] - tls: reject chains containing blocked public keys (Ulises Gascón) #66871935918e342] - tls: reject non-canonical IP addresses (Matteo Collina) nodejs-private/node-private#982de49c913f2] - tls: fix ip normalization regression (James M Snell) nodejs-private/node-private#9859dc4bb57f0] - tools: retry Gatekeeper check and stapling after notarization (Ryan Aslett) #66855oxc-project/oxc (oxfmt)
v0.74.0: oxfmt v0.74.0Compare Source
🐛 Bug Fixes
e236de0formatter_tests: Skip conformance spec calls with non-literal options (#27957) (leaysgur)782ab6elinter: Search string values without UTF-8 conversion (#26716) (Dunqing)a5d8184jsdoc: Parse code spans after quotes in descriptions (#27955) (leaysgur)2645d2cformatter_markdown: Treat link destinations and footnote references as opaque to code span fences (#27948) (leaysgur)4d8195cformatter_yaml: Keep a root plain scalar starting with a document marker verbatim (#27947) (leaysgur)529b057formatter_core: Keep front matter verbatim when body starts with indented delimiter (#27946) (leaysgur)c22a9b2formatter: Treat static block with only empty statements as empty (#27945) (leaysgur)d3ff3f6formatter/jsdoc: Write descriptions as written to not close the comment (#27823) (leaysgur)c4c1727formatter/sort_imports: Keep comments after the last import (#27822) (leaysgur)a64677eformatter: Print JSDoc embedded snippets with LF (#27821) (leaysgur)2c1cc20formatter: Keep comment only Vue bindings as-is (#27820) (leaysgur)1bf236dformatter/sort_imports: Do not use comments as import source (#27819) (leaysgur)52ee29dformatter_yaml: Never start col-0 line with document marker or BOM (#27818) (leaysgur)81c75e7formatter/css: Keep glued css-in-js statement placeholders glued (#27814) (leaysgur)a1ef7f4formatter: Keep typecast parens in same-operator binary and arrow chain (#27812) (leaysgur)de110ceformatter: Keep more parens aroundTSInstantiationExpression(#27811) (leaysgur)8b02e90formatter_json: Reject invalid JSON instead of dropping them (#27785) (leaysgur)6fe4c1bformatter: Treat lone CR in JSX text and argument blank lines (#27780) (leaysgur)5605362oxfmt: Validate editorconfig as like oxfmtrc (#27778) (leaysgur)5b2acb0formatter_core: Report error position releative to CRLF source (#27777) (leaysgur)c78e80eformatter_core: Report parse error positions relative to the BOM-headed source (#27776) (leaysgur)3a980c9formatter_toml: Handle BOM like other languages (#27775) (leaysgur)97c9fc4oxfmt: Handle BOM in config JSON (#27774) (leaysgur)28eb4a7oxfmt: Print trailing newline for--list-different(#27773) (leaysgur)d2bea21formatter: Glue comments to an opener in empty for-head slots and array holes (#27737) (leaysgur)6a95ec1formatter: Keep comment position on holey array (#27730) (leaysgur)54769daformatter: Break after dangling line comment in holey array (#27729) (leaysgur)99077efformatter_json: Reject unary expressions other than signed numbers (#27728) (leaysgur)22cd4cdformatter_json: Handle holey array and comments (#27727) (leaysgur)644ca1cformatter: Do not indent logical chains whose right sides all inline (#27667) (leaysgur)a07a0fbformatter: Wrap comment-only JSX expression container in a group (#27666) (leaysgur)⚡ Performance
e220293formatter: Check only the operator suppression mark inis_quiet(#27952) (leaysgur)e5fdc9cformatter_core: Write into one element stack through a concreteFormatter(#27559) (leaysgur)a342f7eformatter: Skip comment handling for nodes with no comment near them (#27557) (leaysgur)d8ce750formatter: Write string literals with swapped quotes into the arena (#27558) (Yuji Sugiura)1c393c0formatter_core: Skip scanning texts with nothing to rewrite (#27561) (leaysgur)1d3ef10formatter_core: Keep the embedded IR when nothing in it is rewritten (#27673) (leaysgur)📚 Documentation
1325225oxfmt: Update useless comment prefix (#27956) (leaysgur)d0dd140formatter: Note lossy cooked round-trip in template embeds (#27944) (leaysgur)8a3a6c8oxfmt: Update stale notes on the JSDoc string-out channel and fixture origins (#27824) (leaysgur)oxc-project/oxc (oxlint)
v1.89.0Compare Source
🐛 Bug Fixes
9a424c2oxlint,oxfmt: Correct Node.js TypeScript support range (#27699) (camc314)pnpm/pnpm (pnpm)
v12.15.0: pnpm 12.15Compare Source
This release lets
pnpm-workspace.yamldelegate settings to other files and config dependencies withinclude, addslockfile.integrityTarget: tarand tar-registry support, accepts zstd-compressed registry responses, and honorsSOURCE_DATE_EPOCHinpnpm deployandpnpm install. It also rejects registry metadata that names a different package than the one requested and speeds up workspace installs and macOS file linking.Minor Changes
pnpm-workspace.yamlcan now delegate settings to other YAML files and to config dependencies through a newincludefield. Each source may define only the settings the root manifest delegates to it. Every setting has one owner. Commands that change settings write each one to the file that owns it. A relative path in an included file is relative to that file. See Splitting Settings Across Files.A config dependency supplies its settings through the YAML file named in the
pnpm.configfield of itspackage.json. The newbootConfigsetting sets the release-age and trust policy pnpm uses to install config dependencies and the pnpm version frompackageManager.Added the
lockfile.integrityTargetsetting. WithintegrityTarget: tar,pnpm-lock.yamlpins the hash of every package's uncompressed tar, so the lockfile no longer changes when a registry recompresses its tarballs or serves them as tars. pnpm learns a version's tar hash from the store or by downloading it once.pnpm audit signaturesties the tar hash to the signed.tgzintegrity.pnpm can now install from a registry that serves uncompressed tars with zstd or gzip content coding.
pnpm-lock.yamlrecords the hash of each tar. Declare such a registry withserverType: pnprinregistriesto keep tarball URLs out of the lockfile. See Tar registries.pnpm now decodes the content coding of tarball downloads itself. It rejects a zstd response whose window is larger than 8 MiB.
Added the
maxTarballUnpackedSizesetting. It caps the bytes the files of one package may unpack to, 4 GiB by default.Registry revisions now always pin the hash of the uncompressed tar, the original included. pnpm records an original selected through the revision protocol, for example with a
+r0specifier, asrevision: 0in the lockfile and fetches it from the registry's digest route. pnpm checks a revision's tar whether the registry sends it as a tar, gzip, or zstd. Revision metadata must list revision 0 and mark the selected revision. pnpm rejects incomplete revision metadata withERR_PNPM_MALFORMED_METADATA.pnpm now accepts zstd-compressed responses. Registries that serve zstd send package metadata in fewer bytes than with gzip, most of all the full metadata that settings such as
minimumReleaseAgeandtrustPolicyread.pnpm deployandpnpm installnow use theSOURCE_DATE_EPOCHenvironment variable as an upper bound for timestamps innode_modules/.modules.yamlandnode_modules/.pnpm-workspace-state-v1.json. With an equivalently prepared deploy target and an epoch no later than the timestamps that would otherwise be recorded, deploying the same project twice produces identical files #17171.pnpm update --interactivenow highlights the row under the cursor in cyan while keeping the colors of its version changes.Patch Changes
Security
pnpm now fails with
ERR_PNPM_REGISTRY_NAME_MISMATCHif a registry returns metadata for a package other than the one requested. Before, pnpm installed the package under the name in the metadata, soallowBuildsrules for the requested package did not apply to it.minimumReleaseAgeExcludePruneandtrustPolicyExcludePrunenow keep exclusions for resolved configuration dependencies and their transitive dependencies #17142.Resolving dependencies
When
pnpm installresolves a dependency again, it now reuses a version that the install already resolved for the same package, as a fresh install does. Before, it kept the version the lockfile pinned and added a second copy of the package. A locked version still stays when nothing else in the install prefers another version. To pin a transitive dependency on purpose, useoverrides#17084.When another workspace project adds a different version of a package, a project's auto-installed peer on that package now moves to the version a fresh install picks. It used to stay on its locked version while any other project still accepted that version #17058.
A package that lists the same dependency in
dependenciesand as an optional peer now gets the peer bound when a project adds a provider for it later. The lockfile now records every peer a package declares, including one its own dependency supplies #17056.pnpm install --prodandpnpm deploy --prodno longer drop a dependency that a package declares both as an optional peer and as its own dependency, when the package resolved it as its own dependency and a dev dependency provides the same package under another alias.pnpm installwith an existing lockfile and a secondpnpm dedupenow keep optional peer bindings that point into a dependency cycle or back into the dependent package. Before, the second run dropped the optional peer binding from the lockfile snapshot key.pnpm installandpnpm dedupenow preserve own-dependency and peer-dependency bindings when reusing a lockfile whose peer suffixes were hashed bypeersSuffixMaxLength.Upgrading a direct dependency in one workspace project now refreshes matching transitive pins in sibling projects during the same
pnpm installpass.With
resolvePeersFromWorkspaceRoot: false, a workspace project no longer binds a peer to a version that only another project's dependencies provide. pnpm now auto-installs a version that satisfies the peer range for that project. Before, the project got a version outside the range, with no peer warning.pnpm install,pnpm add, andpnpm updatenow reuse the lockfile's resolution for dependencies that take part in a dependency cycle, such asmllyandpkg-types. They re-resolved those packages and everything that depends on them from the registry before pnpm/tasks#130.pnpm now measures a
pnpm.overridesentry written as aworkspace:path, such asworkspace:./packages/foo, from the directory holdingpnpm-workspace.yaml. It used to be measured from each package the override rewrote. The install then linked a directory that does not exist, or failed if workspace packages were injected #17010.pnpm installnow removes config dependencies that are no longer declared, including when the entireconfigDependenciessetting is removed. Frozen installs reject a lockfile that still records removed config dependencies.pnpm install --update-checksumsnow re-resolves every locked package and records the integrity the registry reports now.pnpm addandpnpm installnow acceptgist:<id>dependencies and GitHub Gist URLs, and install them from the gist's archive.pnpm pkg fixnormalizes agist:repository the waynpm pkg fixdoes,pnpm licenseslinks a gist package to its gist page, andpnpm sbomreports the repository of a package whoserepositoryfield is agist:shorthand.pnpm addnow reads the package name correctly from a tarball URL under a registry URL that has a path, such ashttps://example.com/npm/, and installs a registry tarball URL with a malformed percent escape as a plain tarball URL. Before, the registry path became part of the name, so a scoped package failed withERR_PNPM_INVALID_PACKAGE_NAME.With
minimumReleaseAgeset, pnpm now revalidates a package's cached full metadata with a single ETag request so an unchanged registry answers with304, even when the registry does not list a publish time for every version. Previously, pnpm downloaded that metadata again whenever the cached copy was older thanminimumReleaseAge. WithresolutionModeset tolowest-directortime-based, pnpm also reuses that metadata across every workspace project that depends on the package.When pnpm revalidates cached registry metadata, it now sends
If-Modified-Sincewhen the registry's modification time is a date without a time, and no longer crashes when the modification time is before 1970.Added protocol versioning between the pnpm client and pnpr server, verified applied resolution policies in resolution responses, and preserved structured error codes across the wire.
Performance
Sped up
pnpm installon macOS. On a 12-core Mac, installing 1352 packages from a warm store took 1.3 seconds, down from 2.2. pnpm now writes package files intonode_moduleswith 4 threads on macOS, whatever the number of CPU cores. Set thePNPM_MACOS_LINK_THREADSenvironment variable to use a different number of threads, or to0to write files with the threads pnpm uses for the rest of the install.pnpm installis faster and uses less memory in large workspaces withsharedWorkspaceLockfile: false. Each project's install no longer reads the manifests of every other workspace project again. Installs that wait for their workspace dependencies now count towardworkspaceConcurrency#16966.Sped up workspace project discovery, dependency resolution, lockfile up-to-date checks, and peer dependency checks in large workspaces #16839 pnpm/tasks#9. On a workspace with 6,833 projects, the lockfile up-to-date check uses about 1 second less CPU time. The peer dependency check at the end of an install now checks linked workspace projects against the manifests already in memory, without reading each
package.jsonagain.Sped up bin linking and build planning during
pnpm install. Package binary targets and shebang runtimes are now precalculated during tarball extraction and served inpnprregistry metadata alongside verifiedrequiresBuild, tarball size, and file-count metadata.Lowered peak memory when pnpm downloads many packuments, such as during lockfile verification with
trustPolicyon Linux. In one 1,800-entry workspace, a lockfile update now peaks at 1.8 to 2.0 GB. It peaked at 2.6 to 3.7 GB before #17020.pnpm installin a Cargo workspace skips crates that an earlier install already unpacked into the store. Before, a repeat install processed every crate inCargo.lockagain.pnpm install --forceunpacks every crate again pnpm/tasks#69.Linking node_modules and workspaces
Concurrent installs that import the same package into one project now all complete. One of them used to fail with
ENOTEMPTYwhen its copy of the package collided with the copy another install had already placed pnpm/tasks#48.pnpm installnow succeeds whennode_modulesis a symlink to an existing directory. Dependency hoisting previously rejected a symlinkednode_modulesas an invalid destination #17157.A filtered first install under the isolated linker now links every workspace project by name into
node_modules/.pnpm/node_modules, not only the selected ones pnpm/tasks#155.With
nodeLinker: hoisted, a filtered install such aspnpm --filter app add <pkg>keeps the rootnode_moduleslinks and bins of the workspace projects it did not select. A project with no dependencies of its own lost them until the next full install.pnpm install --filterwithnodeLinker: hoistedand--prodor--devnow preserves previously installed dependency groups for unselected workspace projects pnpm/tasks#164. Repeat filtered installs also re-resolve when a transitive injected workspace dependency or a linked dependency's version changes.With
sharedWorkspaceLockfile: false,pnpm installnow runs the workspace root's pnpmfile for every project, after the project's own pnpmfile. Before, it ran only the pnpmfile in the project's directory.pnpm installandpnpm peers checknow detect peer dependency issues and report linked package versions in linked projects that usepackage.json5orpackage.yamlpnpm/tasks#172.pnpm installandpnpm peers checkno longer report an unmet peer when a workspace package's peer is provided by a remote tarball URL. pnpm now compares the peer range with the version in the tarball's manifest #17037.pnpm prunenow removes extraneous direct packages fromnode_moduleswhenpackage.jsonandpnpm-lock.yamlare already in sync.pnpm prunealso honors--filter,--recursive,sharedWorkspaceLockfile: false, and thetrustLockfilesetting and--trust-lockfileflag. With the lockfile trusted,pnpm prune --prodworks offline when every package is in the store #16999.Injected workspace packages
pnpm install --frozen-lockfilenow fails withERR_PNPM_OUTDATED_LOCKFILEwhen a local directory dependency or injected workspace package changes a dependency to a different tarball URL or git commit #17129. It also fails when an injected workspace package changes a dependency's named-registry range, such aswork:^2.0.0, to one the locked version no longer satisfies.pnpm install --frozen-lockfilenow accepts the lockfile it wrote for afile:dependency on a directory without apackage.json. It also accepts the lockfile for an injected workspace package that bundles a dependency inbundledDependencies, lists a dependency in bothdependenciesandoptionalDependencies, or publishes from apublishConfig.directorywhosepackage.jsonlists other dependencies than the project's own. Before, these failed withERR_PNPM_OUTDATED_LOCKFILE.The lockfile now records a
catalog:peer dependency of an injected workspace package as written in itspackage.json. It recorded the catalog's range before, so editing the catalog changed the consumer's lockfile entry pnpm/tasks#153.pnpm installConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ 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.