[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	930b48c
🔍 Latest deploy log	https://app.netlify.com/projects/atlassify/deploys/6ae391a4c0730f344bfd70d4

[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 👍 / 👎}

[gitar-bot]

CI failed: The docs CI check failed because `astro check` does not support TypeScript 7.0, which this Renovate PR upgrades to; the failure is directly caused by the change.

Overview

One unique error template was found across 14 analyzed logs for commit 930b48c. The failure is a single, consistent pattern: astro check rejects the installed TypeScript 7.0 and exits with code 1.

Failures

Astro check incompatible with TypeScript 7.0 (confidence: high)

• Type: dependency
• Affected jobs: 123652739194
• Related to change: yes
• Root cause: The astro check step reports [ERROR] [check] astro check does not currently support TypeScript 7.0. To continue using astro check, install TypeScript 6 instead. The PR bumps TypeScript to v7, so the incompatibility is introduced by this change. The log also notes that astro check will be deprecated and that TypeScript 7.1+ type-checking for Astro files is available through @astrojs packages.
• Suggested fix: Keep the docs package on TypeScript 6 for the astro check step, or migrate to the TypeScript 7.1+ checking approach described by Astro (see its README) before merging this upgrade.

Summary

• Change-related failures: 1 failure (astro check step failing on TypeScript 7.0 support) in job 123652739194.
• Infrastructure/flaky failures: None identified. The pnpm setup, cache restore, and git init steps completed normally; the hint and cache messages are not failures.
• Recommended action: Do not merge the TypeScript v7 bump as-is. Either pin TypeScript to 6.x for the docs/astro check path or move to the Astro TypeScript 7.1+ checking setup, then rerun CI.

Code Review 🚫 Blocked 0 closed / 1 findings

🟡 Medium risk · Upgrading the documentation package from TypeScript 6 to 7 could disrupt documentation builds or type-checking through compiler incompatibilities.

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}