-
-
Notifications
You must be signed in to change notification settings - Fork 3
fix(deps): update patch updates (patch) #921
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
Thank you for following the naming conventions! 🙏 |
4040346
to
83539da
Compare
df346cf
to
e92d474
Compare
cf92e8a
to
6d12918
Compare
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
27f0a80
to
8f6e3c8
Compare
8f6e3c8
to
9a5b141
Compare
Signed-off-by: Renovate Bot <[email protected]>
9a5b141
to
f9ea33b
Compare
This PR contains the following updates:
^1.52.2
->^1.52.6
^1.52.3
->^1.52.6
^1.3.1
->^1.3.2
>=0.3.3
->>=0.3.5
4.25.1
->4.25.3
^1.0.30001731
->^1.0.30001735
>=2.8.3
->>=2.8.4
^0.25.8
->^0.25.9
>=0.25.6
->>=0.25.9
^16.1.4
->^16.1.5
^0.0.54
->^0.0.55
^4.20.3
->^4.20.4
Release Notes
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v1.52.6
Compare Source
🐞 Fixes
naming-convention/component-name
validation to continue on valid names, closes #1176 by @Rel1cx in #1177Full Changelog: Rel1cx/eslint-react@v1.52.5...v1.52.6
v1.52.5
Compare Source
🐞 Fixes
is-from-react
utility inreact-debug/is-from-react
rule and improvereact-x/no-forward-ref
rule autofix handling, closes #1172 by @Rel1cx in https://github.com/Rel1cx/eslint-react/pull/1173Full Changelog: Rel1cx/eslint-react@v1.52.4...v1.52.5
v1.52.4
Compare Source
🐞 Fixes
Full Changelog: Rel1cx/eslint-react@v1.52.3...v1.52.4
v1.52.3
Compare Source
🐞 Fixes
bun
engine requirement frompackage.json
files, closes #1157 by @Rel1cx in https://github.com/Rel1cx/eslint-react/pull/1158Full Changelog: Rel1cx/eslint-react@v1.52.2...v1.52.3
eslint/rewrite (@eslint/compat)
v1.3.2
Compare Source
Dependencies
eslint/rewrite (@eslint/plugin-kit@<0.3.3)
v0.3.5
Compare Source
Dependencies
v0.3.4
Compare Source
Bug Fixes
browserslist/browserslist (browserslist)
v4.25.3
Compare Source
v4.25.2
Compare Source
--permission
support (by @broofa).browserslist/caniuse-lite (caniuse-lite)
v1.0.30001735
Compare Source
v1.0.30001734
Compare Source
v1.0.30001733
Compare Source
wanasit/chrono (chrono-node@<2.2.4)
v2.8.4
Compare Source
958eb3d
a5c52cf
.evanw/esbuild (esbuild)
v0.25.9
Compare Source
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:
drive. The problem was as follows:C:
driveD:
drive../..
to get from the project directory to the cache directory..
(soD:\..
is justD:
)Yarn works around this edge case by pretending Windows-style paths beginning with
C:\
are actually Unix-style paths beginning with/C:/
, so the../..
path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
lint-staged/lint-staged (lint-staged)
v16.1.5
Compare Source
Patch Changes
4e3ce22
Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.stackblitz-labs/pkg.pr.new (pkg-pr-new)
v0.0.55
Compare Source
privatenumber/tsx (tsx)
v4.20.4
Compare Source
Configuration
📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 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.