⬆️ Update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.9.3 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
shiny-poems	Error		May 19, 2026 1:25am

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: tools/poem-admin/pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (58 entries)...
✗ Lockfile failed supply-chain policy check (58 entries in 1.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @types/node@25.9.0 was published at 2026-05-18T12:44:00.435Z, within the minimumReleaseAge cutoff (2026-05-18T01:25:30.092Z)

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.

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (806 entries)...
✗ Lockfile failed supply-chain policy check (806 entries in 5.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  tsx@4.22.2 was published at 2026-05-18T14:13:45.000Z, within the minimumReleaseAge cutoff (2026-05-18T01:25:37.319Z)

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.