chore(deps): lock file maintenance

[renovate]

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, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

---

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

---

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​rocicorp/​zero@​1.8.0
	typescript@​7.0.2
	knip@​6.27.0
	eslint@​10.7.0

View full report

[socket-security]

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		Obfuscated code: npm rimraf is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@rocicorp/zero@1.8.0 → npm/rimraf@5.0.10 ℹ 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/rimraf@5.0.10. 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		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@rocicorp/zero@1.8.0 → npm/yargs@17.7.3 ℹ 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/yargs@17.7.3. 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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 3 workspace projects
? Verifying lockfile against supply-chain policies (1553 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated @rocicorp/resolver@1.0.2
Progress: resolved 26, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 29, reused 0, downloaded 0, added 0
Progress: resolved 193, reused 0, downloaded 0, added 0
Progress: resolved 289, reused 0, downloaded 0, added 0
Progress: resolved 361, reused 0, downloaded 0, added 0
Progress: resolved 410, reused 0, downloaded 0, added 0
Progress: resolved 482, reused 0, downloaded 0, added 0
Progress: resolved 577, reused 0, downloaded 0, added 0
Progress: resolved 659, reused 0, downloaded 0, added 0
Progress: resolved 728, reused 0, downloaded 0, added 0
Progress: resolved 780, reused 0, downloaded 0, added 0
Progress: resolved 801, reused 0, downloaded 0, added 0
Progress: resolved 839, reused 0, downloaded 0, added 0
Progress: resolved 842, reused 0, downloaded 0, added 0
Progress: resolved 868, reused 0, downloaded 0, added 0
Progress: resolved 915, reused 0, downloaded 0, added 0
Progress: resolved 963, reused 0, downloaded 0, added 0
Progress: resolved 1015, reused 0, downloaded 0, added 0
Progress: resolved 1037, reused 0, downloaded 0, added 0
Progress: resolved 1038, reused 0, downloaded 0, added 0
Progress: resolved 1113, reused 0, downloaded 0, added 0
Progress: resolved 1210, reused 0, downloaded 0, added 0
Progress: resolved 1296, reused 0, downloaded 0, added 0
Progress: resolved 1394, reused 0, downloaded 0, added 0
Progress: resolved 1516, reused 0, downloaded 0, added 0
Progress: resolved 1527, reused 0, downloaded 0, added 0
Progress: resolved 1545, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1553 entries in 32.2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  tsdown@0.22.14 was published at 2026-07-23T18:23:34.000Z, within the minimumReleaseAge cutoff (2026-07-23T18:14:30.989Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
[WARN] 4 deprecated subdependencies found: glob@10.5.0, node-domexception@1.0.0, prebuild-install@7.1.3, uuid@8.3.2
Progress: resolved 1546, reused 0, downloaded 0, added 0