Update all-deps to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Confidence
actions/setup-node	action	major	v6 → v7
typescript (source)	devDependencies	major	^6.0.0 → ^7.0.0

---

Release Notes

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

What's Changed

Enhancements:

• Add cache-primary-key and cache-matched-key as outputs by @​gowridurgad in #​1577
• Migrate to ESM and upgrade dependencies by @​gowridurgad in #​1574

Bug fixes:

• Remove dummy NODE_AUTH_TOKEN export by @​gowridurgad in #​1558
• Only use mirrorToken in getManifest if it's provided by @​deiga in #​1548

Documentation updates:

• Add documentation for publishing to npm with Trusted Publisher (OIDC) by @​chiranjib-swain in #​1536
• docs: Update restore-only cache documentation by @​priya-kinthali in #​1550
• docs: Update caching recommendations to mitigate cache poisoning risks by @​chiranjib-swain in #​1567

Dependency update:

• Upgrade @​actions/cache to 5.1.0, log cache write denied by @​jasongin in #​1569

New Contributors

• @​chiranjib-swain made their first contribution in #​1536
• @​deiga made their first contribution in #​1548
• @​jasongin made their first contribution in #​1569

Full Changelog: actions/setup-node@v6...v7.0.0

v7

Compare Source

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

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

---

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

---

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

[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: docs/pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (1516 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 17, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1516 entries in 3.4s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification:
  @takumi-rs/core-darwin-arm64@2.3.0 was published at 2026-07-17T14:24:14.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-darwin-x64@2.3.0 was published at 2026-07-17T14:24:09.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-linux-arm64-gnu@2.3.0 was published at 2026-07-17T14:24:20.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-linux-arm64-musl@2.3.0 was published at 2026-07-17T14:24:26.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-linux-x64-gnu@2.3.0 was published at 2026-07-17T14:24:36.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-linux-x64-musl@2.3.0 was published at 2026-07-17T14:24:41.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-win32-arm64-msvc@2.3.0 was published at 2026-07-17T14:24:31.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core-win32-x64-msvc@2.3.0 was published at 2026-07-17T14:24:46.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/core@2.3.0 was published at 2026-07-17T14:24:50.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)
  @takumi-rs/helpers@2.3.0 was published at 2026-07-17T14:24:02.000Z, within the minimumReleaseAge cutoff (2026-07-17T08:25:03.192Z)

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.