Repository navigation
fix(deps): update minor updates (minor) - #1233
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Signed-off-by: Renovate Bot <bot@renovateapp.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
browserslist-config-anolilab
@anolilab/commitlint-config
@anolilab/eslint-config
@anolilab/lint-staged-config
@anolilab/oxfmt-config
@anolilab/oxlint-config
@anolilab/prettier-config
@anolilab/stylelint-config
@anolilab/textlint-config
commit: |
Member
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.24.10→5.26.50.72.0→0.73.012.11.2→12.13.0Release Notes
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.26.5Compare Source
🐞 Fixes
react-x/set-state-in-effect: asetStateon the right side of a short-circuit operator (&&,||,??) is now exempt when the left operand is ref-derived (ex:ref.current && setData(1)), matching the existing ref-gated conditional exemption; a left-sidesetStatestill runs unconditionally and stays reported. (#2031)react-x/set-state-in-effect: setup identifiers are now collected from the setup argument of the effect call only; the callee and the deps array are no longer scanned, so a function referenced only in the deps array (ex:useEffect(setup, [helper])) is no longer mistaken for the setup and itssetStatecalls stay unattributed. (#2031)react-x/set-state-in-effect: arrow function parameters are no longer collected as callback-body setter references (ex: thesetStateinuseMemo((setState) => ..., [])); only actual callback bodies are collected (ex:useMemo(() => setState, [])). (#2031)Full Changelog: Rel1cx/eslint-react@v5.26.4...v5.26.5
v5.26.4Compare Source
🐞 Fixes
export const useAnchor = () => useRef(null)) are no longer misreported; calls inside JSX expressions, computed keys, or class static blocks no longer fall back to the outer variable. (#2029) Closes #2026. Affected rules:react-naming-convention/context-namereact-naming-convention/id-namereact-naming-convention/ref-nameconst refs = [useRef(null)],const n = useRef(0) + 1), so such calls are no longer reported on the enclosing variable; sequence expressions check only the last value, and unresolvable computed keys (ex:{ [key]: useRef(null) }) no longer fall back to the outer variable. (#2030) Affected rules:react-naming-convention/context-namereact-naming-convention/id-namereact-naming-convention/ref-nameFull Changelog: Rel1cx/eslint-react@v5.26.3...v5.26.4
v5.26.3Compare Source
🐞 Fixes
const refs = { myRef: useRef(0) }); computed keys with string literals (ex:refs["value"] = useRef(null)) are now checked, and unresolvable computed keys are no longer reported. (#2028) Affected rules:react-naming-convention/context-namereact-naming-convention/id-namereact-naming-convention/ref-namereact-naming-convention/ref-name: immediate dereferences of theuseRefresult through TypeScript type wrappers (ex:(useRef(null) as { current: null }).current,useRef(null)!.current) are no longer reported, extending the #1375 fix. (#2028)Full Changelog: Rel1cx/eslint-react@v5.26.2...v5.26.3
v5.26.2Compare Source
✨ New
react-x/no-unused-props: improved prop usage detection. Props parameters with default values (ex:function Component(props: Props = defaultProps)) are now unwrapped and analyzed, props aliased to a local variable (ex:const alias = props) are tracked through the alias, and template literals without substitutions (ex:props[`foo`]) are recognized as static prop keys. (#2021)🐞 Fixes
react-x/no-unused-props: a component whose used prop keys cannot be fully determined (ex: it passes the whole props object to another function) now marks all of its declared props as used, so a props declaration shared with another fully analyzable component is no longer reported as unused. (#2021)react-x/set-state-in-effect: ref-derived values that reach thesetStateargument through assignment statements (rather than the declaration initializer) are now recognized; only writes that lexically precede the use and live in the use's own function or an ancestor count. (#2027)react-x/set-state-in-effect: parameters of a helper invoked from the effect setup are now treated as ref-derived when the call-site argument is ref-derived, matched per call site by parameter definition. (#2027)react-x/set-state-in-effect: a.currentread rooted at a function parameter is now recognized as a ref read (ex:setReferenceElement(anchor?.current)whereanchoris aRefObjectprop); previously only parameters namedrefor ending inRefwere recognized. (#2027)react-x/no-unused-class-component-members: public methods (including function-valued properties) of an exported class component are no longer reported as unused, as they may be part of the component's imperative API invoked by consumers through refs. Data fields,private/protectedmembers, and members of non-exported classes are still reported. (#2024)🏗️ Internal
react-dom,react-jsx,react-web-api, andreact-xrules. (#2022)Full Changelog: Rel1cx/eslint-react@v5.26.1...v5.26.2
v5.26.1Compare Source
🏗️ Internal
"replace"to"suggest". Affected rules:react-x/no-context-providerreact-x/no-forward-refreact-x/no-use-contextreact-x/immutability: moved context-dependent helpers fromhelpers.tsintoorigins.tsandeffects.tsto match the fact-based implementation pattern.react-x/globals: movedresolveToFunctionfromhelpers.tstoorigins.ts.effectto4.0.3,tsl-dxto0.14.1,@tsconfig/node20to20.1.10, and@types/nodeto20.19.43.📝 Documentation
react-xrules.Full Changelog: Rel1cx/eslint-react@v5.26.0...v5.26.1
v5.26.0Compare Source
✨ New
>=22.0.0to>=20.19.0. (#2020)Full Changelog: Rel1cx/eslint-react@v5.25.0...v5.26.0
v5.25.0Compare Source
✨ New
react-dom/no-unsafe-target-blank: added anallowReferreroption (default:false). When enabled,rel="noopener"alone is accepted and the suggested fix addsrel="noopener"instead ofrel="noreferrer noopener", preserving referrer information while still requiring an explicit token. (#2019) Closes #2012.🏗️ Internal
@eslint-react/ast: addedhasParentandhasEnclosingTryBlockshortcuts toTraverse. (#2016)@eslint-react/ast: renamed thetypesmodule totreeand narrowed theExtract.unwrapresult type. (#2017)@eslint-react/core: removed the unusedREACT_BUILTIN_HOOK_NAMESconstant.tsdownto0.23.1,@effect/platform-nodeto4.0.3,pnpmto12.11.2,@types/nodeto26.6.5,setup-uvtov10.3.0, andfumadocsandlucide-reactin the website.Full Changelog: Rel1cx/eslint-react@v5.24.10...v5.25.0
oxc-project/oxc (oxfmt)
v0.73.0Compare Source
🚀 Features
a495e82oxfmt: Supportassociationsconfig to specify language over filepath (#27437) (leaysgur)5db28faoxfmt: Support Astro viaprettier-plugin-astro@1.x(#27386) (leaysgur)📚 Documentation
408d87foxfmt: Simplify oxfmtrc docs (#27432) (leaysgur)902e188oxfmt: Update howembeddedLanguageFormattingoption works (#27362) (leaysgur)pnpm/pnpm (pnpm)
v12.13.0: pnpm 12.13.0Compare Source
This release adds the
pnpm profileandpnpm tokencommands, thestoreIndexFormat: filessetting for stores shared over a network filesystem, and faster Python dependency resolution.Minor Changes
Added the
pnpm profilecommand to view and update registry user profile settings.Added
pnpm tokento list, create, and revoke authentication tokens on the registry.Added the
storeIndexFormatsetting. Set it tofilesto keep a store's package index as one file per package instead of the SQLiteindex.db, for a store on a network filesystem that several machines use at once. SQLite's locking does not work across machines, so concurrent installs on such a store could corruptindex.db.Added the
nodePackageMapsetting, which groups the package-map settings.nodePackageMap.mode: write-onlywritesnode_modules/.package-map.jsonfor other tools without making Node.js load it.mode: loadalso makes Node.js load the map, likenodeExperimentalPackageMap: true.nodePackageMap.typereplacesnodePackageMapType. The old settings still work #14937.Patch Changes
Setting up pnpm
pnpm setupnow works when pnpm was installed with npm on macOS. It installed pnpm from npm'sbindirectory and left a$PNPM_HOME/bin/pnpmthat could not run #16855.pnpm runs again after
pnpm setupwhenglobalShimsenables pnpm. Every command failed with "the global target of the pnpm shim points back at the shim" #16874.A pnpm built for the MinGW target on Windows, such as the MSYS2 package, now installs the MinGW Rust toolchain that
rust-toolchain.tomlnames. It used to install the MSVC toolchain.Installing packages
On macOS,
pnpm installno longer fails withERR_PNPM_LOCKFILE_WRITE_FILEwhen the project is on a virtiofs or SMB share. pnpm now falls back to a regularfsyncwhen the file system rejects a full sync #16846.On macOS,
pnpm install,pnpm patch-commit, and other commands that load a pnpmfile no longer hang at random.pnpm installnow puts the executables of a Python build backend's requirements on thePATHwhile the backend runs. Projects built withuv_buildnow install. Before, they failed with "uv-build was not properly installed".Removing a
link:dependency now also removes its symlink fromnode_moduleswhennodeLinkerishoisted#16884.pnpm-lock.yamlno longer records the tarball URL of a package installed from a scoped registry, such as one set by@types:registry=, when pnpm can rebuild the URL from that registry #16866.Packing, auditing, and pipelines
pnpm packandpnpm publishnow pack onlypackage.json, the README, the license, and the files named inmainandbinwhenfilesis an empty array. They used to pack every file in the package #16889.pnpm auditandpnpm audit signaturesno longer check runtimes installed throughdevEngines.runtime, such asnode@runtime:24.21.0, against the npm package of the same name.pnpm audit signaturesreported these runtimes as having an invalid registry signature #16869.pnpm pipelinenow runs the root's tasks whenpnpm-workspace.yamllists only the root inpackagesor omitspackages, aspnpm -r rundoes. A change to a root file in such a workspace no longer triggers a full-run warning. When a full run has no projects to run,pnpm pipelinenow reports that no projects are selected #16849.Performance
pnpm installresolves Python dependencies faster. With--lockfile-only, a project with 10 dependencies now resolves in about 4 seconds, down from about 40. When the index publishes a metadata file beside each wheel (PEP 658), as PyPI does, pnpm downloads only the wheels of the releases it selects.A repeat install against an existing lockfile no longer reads registry metadata for the dependencies it takes from that lockfile. On a warm store this removes thousands of metadata lookups from a repeat install of a large workspace.
pnpm installwithenableModulesDir: falsenow verifies the packages already in the store while the dependencies resolve, and checks a package's files in parallel. On a 5,100-package install with the store on a network filesystem, this removed a 19-second pause between resolution and fetching.Platinum Sponsors
Gold Sponsors
v12.12.1: pnpm 12.12.1Compare Source
This release adds OIDC authentication to
pnpm dist-tagand thetool:protocol.pnpm publishnow checks which registry anNPM_ID_TOKENwas issued for before using it.Patch Changes
pnpm publishnow uses anNPM_ID_TOKENonly if itsaudclaim matches the selected registry, such asnpm:registry.npmjs.org. A token for another registry is skipped with a warning, and pnpm falls back to the configured credentials.pnpm dist-tag add,rm, andlsnow support OIDC authentication in CI. Enable "Allow npm dist-tag" in the package's trusted publishing settings to manage tags without a stored npm token.Added the
tool:protocol for the tools pnpm downloads itself: Node.js, Bun, Deno, and Yarn.pnpm add bun@tool:1.3.0,pnx node@tool:22, andpnx yarn@tool:4work like theruntime:spelling, which stays supported as an alias. A lockfile written forruntime:stays up to date whenpackage.jsonswitches totool:, and the other way around.A named registry can no longer be called
tool.Platinum Sponsors
Gold Sponsors
v12.12.0: pnpm 12.12.0Compare Source
This release shares task results and dependency builds through a remote cache, adds the
addMissingPeerTypessetting, and letspnpm add --configandpnpm updatemanage configuration dependencies. It also fixesdangerouslyAllowAllBuildsrunning the build scripts of packages thatallowBuildsdenies.Minor Changes
pnpm pipelinecan share task results between machines. A result is a signed artifact stored on a pnpr server or on a server that speaks the Turborepo Remote Cache API, such as Vercel Remote Cache.The remote side-effects cache can also store dependency builds on a Turborepo Remote Cache server. Both caches read the new
remoteCachesetting, which names the server and holds the signing keys.pnpm pipeline --reportrecords the run under the organizationremoteCache.orgnames.Added the
addMissingPeerTypessetting, which links the@typespackage of a peer dependency next to every package that peer-depends on it. For example, a package that peer-depends onreactgets the project's@types/reactlinked next to it. This lets TypeScript find the types of a peer dependency when the global virtual store is on #15689.pnpm add --configandpnpm updatenow handle configuration dependencies the way they handle other dependencies #16814.pnpm add --configsaves a version range inpnpm-workspace.yamlby the same rules aspnpm add, sopnpm add --config my-config@latestsaves a range such as^1.2.0. It also resolves the package again whenpnpm-lock.yamlalready locks an older version.pnpm updateupdates configuration dependencies within their ranges, andpnpm update --latestmoves them to their latest version. A selector such aspnpm update my-configupdates only the configuration dependencies it names.Patch Changes
A package set to
falseinallowBuildsno longer runs its build scripts whendangerouslyAllowAllBuildsistrue. The two settings together now allow every build except the denied ones. Previously,dangerouslyAllowAllBuildsignored the denials.pnpm now switches to the pnpm version a project pins even when it cannot read its configuration. Previously, a setting it rejected in the global config file, an
.npmrcfile, or_auth, or apnpm-workspace.yamlit could not parse, stopped every command,pnpm --versionincluded.pnpm updateandpnpm whyaccept--depth Infinityagain. They failed withinvalid value 'Infinity' for '--depth <DEPTH>'#16817.pnpm deploywithoutinjectWorkspacePackagesnow binds a peer dependency of a linked workspace package to the version its parent provides, as an injected install does. Previously the deploy failed withERR_PNPM_DEPLOY_AMBIGUOUS_PEERwhenever other packages in the deployed graph depended on different versions of that peer #16807.pnpm deploy --legacyno longer fails withERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVERwhen a workspace dependency of the deployed project declares aworkspace:peer dependency that the project does not depend on itself. pnpm now copies that peer from the workspace into the deploy directory.An auto-installed peer declared with
workspace:now always resolves to the workspace project. Previously,workspace:*andworkspace:^1.0.0peers could be installed from the registry #16806.Repeat installs no longer resolve again when an injected workspace package lists a dependency also as a peer dependency.
Sped up frozen installs of unchanged injected workspace packages that use hardlinks.
Sped up workspace discovery with subtree exclusions such as
!generated/**.A key under a registry URL in the
_authsetting that does not start with@is now skipped with a warning, so a field a later pnpm version adds there no longer breaks this one. A key that holds anauthTokenobject but lacks its@, such asorgfor@org, is still an error.Platinum Sponsors
Gold Sponsors
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.