Skip to content

chore(deps): lock file maintenance - #240

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#240
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies label Aug 1, 2026
@nx-cloud

nx-cloud Bot commented Aug 1, 2026 •
edited
Loading

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit c9938c6

Command Status Duration Result
nx run-many --targets=build --exclude=examples/** ✅ Succeeded 17s View ↗

☁️ Nx Cloud last updated this comment at 2026-08-01 00:58:48 UTC

@socket-security

socket-security Bot commented Aug 1, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addednx@​22.7.85310092100100
Addedhappy-dom@​20.11.1661008896100
Added@​tanstack/​react-query-devtools@​5.101.41001007098100
Added@​tanstack/​devtools-utils@​0.5.1991007293100
Added@​tanstack/​preact-devtools@​0.10.9741008797100
Added@​angular/​platform-browser@​21.2.19771007598100
Added@​types/​react-dom@​19.2.41001007584100
Added@​angular/​compiler-cli@​21.2.19811007698100
Added@​angular/​cli@​21.2.19771007898100
Added@​angular/​router@​21.2.19791007798100
Added@​angular/​forms@​21.2.19801007798100
Added@​angular/​compiler@​21.2.19801007896100
Added@​angular/​build@​21.2.19811007898100
Added@​angular/​core@​21.2.19811007896100
Added@​types/​react@​19.2.181001007992100
Addedvitest@​4.1.10981007999100
Added@​angular/​common@​21.2.191001007998100
Added@​faker-js/​faker@​10.5.01001001009080
Added@​types/​node@​25.9.51001008195100
Addedpublint@​0.3.22991008185100
Added@​tanstack/​devtools-event-client@​0.4.41001008294100
Addedvite@​8.2.0991008298100
Addedreact@​19.2.81001008497100
Addedmarkdown-link-extractor@​4.0.41001008687100
Added@​tanstack/​react-query@​5.101.4991008797100
Addedtsdown@​0.22.14981008898100
Addedsherif@​1.13.09910010091100
Addedreact-dom@​19.2.81001009298100
Added@​preact/​preset-vite@​2.10.69910010092100
Addedknip@​6.29.0971009596100
Added@​vitejs/​plugin-react@​6.0.510010010095100
Addedeslint@​10.8.09710010095100
Added@​testing-library/​jest-dom@​6.10.010010010096100
See 6 more rows in the dashboard

View full report

@socket-security

socket-security Bot commented Aug 1, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @angular/build is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: examples/angular/asyncBatch/package.json → npm/@angular/build@21.2.19

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular/build@21.2.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @angular/cli is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: examples/angular/asyncBatch/package.json → npm/@angular/cli@21.2.19

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular/cli@21.2.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @schematics/angular is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/@angular/cli@21.2.19 → npm/@schematics/angular@21.2.19

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@schematics/angular@21.2.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Publisher changed: npm @solid-primitives/keyboard is now published by davedbase

Author: davedbase

From: pnpm-lock.yaml → npm/@tanstack/solid-devtools@0.8.5 → npm/@tanstack/react-devtools@0.10.5 → npm/@tanstack/preact-devtools@0.10.9 → npm/@solid-primitives/keyboard@1.3.7

ℹ Read more on: This package | This alert | What is unstable ownership?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@solid-primitives/keyboard@1.3.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm happy-dom is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.json → npm/happy-dom@20.11.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/happy-dom@20.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm seroval is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/solid-js@1.9.14 → npm/seroval@1.5.6

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/seroval@1.5.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
Low adoption: npm eslint-plugin-react-jsx

Location: Package overview

From: pnpm-lock.yaml → npm/@eslint-react/eslint-plugin@5.18.1 → npm/eslint-plugin-react-jsx@5.18.1

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-react-jsx@5.18.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@pkg-pr-new

pkg-pr-new Bot commented Aug 1, 2026

Copy link
Copy Markdown
More templates

@tanstack/angular-pacer

npm i https://pkg.pr.new/@tanstack/angular-pacer@240

@tanstack/pacer

npm i https://pkg.pr.new/@tanstack/pacer@240

@tanstack/pacer-devtools

npm i https://pkg.pr.new/@tanstack/pacer-devtools@240

@tanstack/pacer-lite

npm i https://pkg.pr.new/@tanstack/pacer-lite@240

@tanstack/preact-pacer

npm i https://pkg.pr.new/@tanstack/preact-pacer@240

@tanstack/preact-pacer-devtools

npm i https://pkg.pr.new/@tanstack/preact-pacer-devtools@240

@tanstack/react-pacer

npm i https://pkg.pr.new/@tanstack/react-pacer@240

@tanstack/react-pacer-devtools

npm i https://pkg.pr.new/@tanstack/react-pacer-devtools@240

@tanstack/solid-pacer

npm i https://pkg.pr.new/@tanstack/solid-pacer@240

@tanstack/solid-pacer-devtools

npm i https://pkg.pr.new/@tanstack/solid-pacer-devtools@240

commit: bdbe318

@renovate

renovate Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants