[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	6.0.3 → 7.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2: TypeScript 7.0.2

Compare Source

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

---

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: Disabled by config. Please merge this manually once you are satisfied.

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

[netlify]

✅ Deploy Preview for atlassify canceled.

Name	Link
🔨 Latest commit	49afaa3
🔍 Latest deploy log	https://app.netlify.com/projects/atlassify/deploys/6aeb1c58910fe44ae5bda5ba

[gitar-bot]

🚨 Bug: TS 7 is outside @astrojs/check's peer range; breaks pnpm build

The lockfile shows @astrojs/check@0.9.10 declares peerDependencies: typescript: ^5.0.0 || ^6.0.0 (pnpm-lock.yaml:240-241), but pnpm now resolves it against typescript@7.0.2 (pnpm-lock.yaml:211, 2699-2704). TypeScript 7 is the native Go port: the npm package installs a tsc binary plus the platform-specific @typescript/typescript-* binaries, and it does not ship the JavaScript compiler API that @astrojs/language-server, @volar/typescript and volar-service-typescript load. In docs/package.json, build runs pnpm check && astro build, and check runs astro check. So the docs build will fail when it type-checks, or at best run with an unsupported peer version. Keep typescript on 6.x until @astrojs/check supports 7, or install both versions side by side so Astro tooling still finds the 6.x JS API. Either way, tell Renovate to skip TS 7 for now.

Revert to TypeScript 6 until @astrojs/check / language-server support TS 7, and add a Renovate rule to ignore typescript major 7 for now.:

"typescript": "6.0.3"

• Apply fix

_{Check the box to apply the fix or reply for a change | Was this helpful? React with 👍 / 👎}

[setchy]

PR workflows are currently failing because @astrojs/check isn’t compatible with TypeScript 7.1. Its replacement, @astrojs/ts-content-mapper, is still in beta, so we’re waiting on a stable release.

[gitar-bot]

CI failed: Two docs CI jobs fail because `astro check` does not support TypeScript 7.0, which this PR upgrades from 6.0.3 to 7.0.2 in docs/package.json; the chained build in the second job stops before `astro build` runs.

Overview

Two unique error templates were found across 34 logs (commit 49afaa3). Both point to the same root cause: Astro's astro check rejects TypeScript 7.0. The assessment is high confidence and change-related.

Failures

astro check does not support TypeScript 7.0 (confidence: high)

• Type: dependency
• Affected jobs: 126555259216, 126555258828
• Related to change: yes
• Root cause: Astro logs [ERROR] [check] astro check does not currently support TypeScript 7.0. To continue using astro check, install TypeScript 6 instead. The PR changes docs/package.json from TypeScript 6.0.3 to 7.0.2, which introduces the unsupported version. In job 126555258828 the failure occurs in pnpm <*> && astro build, so the chained build stops after astro check exits with code 1.
• Suggested fix: Pin TypeScript to 6.x for the docs package (docs/package.json) until astro check supports TypeScript 7. Alternatively, migrate to the experimental Astro TypeScript 7.1+ checking setup (@astrojs/ts-content-mapper, per the log's README reference) if that fits the project. Note that the analyzer's suggested fix refers to a @astrojs package name that was truncated in the log, so verify the exact package before adopting it.

Summary

• Change-related failures: 2 jobs (126555259216, 126555258828) fail from the TypeScript 7.0 upgrade in docs/package.json.
• Infrastructure/flaky failures: None identified. The git init hints and pnpm cache messages are informational only.
• Recommended action: Revert the docs package to TypeScript 6.x, or hold this Renovate update until Astro supports TypeScript 7 in astro check, then rerun the docs jobs.

Code Review 🚫 Blocked 0 closed / 1 findings

🟡 Medium risk · Upgrading the docs TypeScript compiler from 6 to 7 could change type-checking or documentation build behavior.

Bumps typescript from 6.0.3 to 7.0.2 via Renovate, but the change is blocked by a critical issue: @astrojs/check@0.9.10 only declares a peer range of ^5.0.0 || ^6.0.0, and pnpm now resolves it against TypeScript 7, which ships a native Go binary without the JavaScript compiler API that the Astro tooling loads. This will break pnpm build in docs/ at the astro check step, so the update should stay on 6.x until @astrojs/check supports 7.

🚨 Bug: TS 7 is outside @astrojs/check's peer range; breaks pnpm build

📄 docs/package.json:61 📄 docs/pnpm-lock.yaml:211 📄 docs/pnpm-lock.yaml:240-241 📄 docs/pnpm-lock.yaml:2346-2349 📄 docs/pnpm-lock.yaml:2699-2704

The lockfile shows @astrojs/check@0.9.10 declares peerDependencies: typescript: ^5.0.0 || ^6.0.0 (pnpm-lock.yaml:240-241), but pnpm now resolves it against typescript@7.0.2 (pnpm-lock.yaml:211, 2699-2704). TypeScript 7 is the native Go port: the npm package installs a tsc binary plus the platform-specific @typescript/typescript-* binaries, and it does not ship the JavaScript compiler API that @astrojs/language-server, @volar/typescript and volar-service-typescript load. In docs/package.json, build runs pnpm check && astro build, and check runs astro check. So the docs build will fail when it type-checks, or at best run with an unsupported peer version. Keep typescript on 6.x until @astrojs/check supports 7, or install both versions side by side so Astro tooling still finds the 6.x JS API. Either way, tell Renovate to skip TS 7 for now.

Revert to TypeScript 6 until @astrojs/check / language-server support TS 7, and add a Renovate rule to ignore typescript major 7 for now.

"typescript": "6.0.3"

🤖 Prompt for agents

Code Review: Bumps `typescript` from 6.0.3 to 7.0.2 via Renovate, but the change is blocked by a critical issue: `@astrojs/check@0.9.10` only declares a peer range of `^5.0.0 || ^6.0.0`, and pnpm now resolves it against TypeScript 7, which ships a native Go binary without the JavaScript compiler API that the Astro tooling loads. This will break `pnpm build` in `docs/` at the `astro check` step, so the update should stay on 6.x until `@astrojs/check` supports 7.

1. 🚨 Bug: TS 7 is outside @astrojs/check's peer range; breaks `pnpm build`
   Files: docs/package.json:61, docs/pnpm-lock.yaml:211, docs/pnpm-lock.yaml:240-241, docs/pnpm-lock.yaml:2346-2349, docs/pnpm-lock.yaml:2699-2704

   The lockfile shows `@astrojs/check@0.9.10` declares `peerDependencies: typescript: ^5.0.0 || ^6.0.0` (pnpm-lock.yaml:240-241), but pnpm now resolves it against `typescript@7.0.2` (pnpm-lock.yaml:211, 2699-2704). TypeScript 7 is the native Go port: the npm package installs a `tsc` binary plus the platform-specific `@typescript/typescript-*` binaries, and it does not ship the JavaScript compiler API that `@astrojs/language-server`, `@volar/typescript` and `volar-service-typescript` load. In `docs/package.json`, `build` runs `pnpm check && astro build`, and `check` runs `astro check`. So the docs build will fail when it type-checks, or at best run with an unsupported peer version. Keep `typescript` on 6.x until `@astrojs/check` supports 7, or install both versions side by side so Astro tooling still finds the 6.x JS API. Either way, tell Renovate to skip TS 7 for now.

   Fix (Revert to TypeScript 6 until @astrojs/check / language-server support TS 7, and add a Renovate rule to ignore typescript major 7 for now.):
   "typescript": "6.0.3"

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}