ci(dependabot): ignore TypeScript major bumps until the lint toolchain supports TS7

[BigSimmo]

Summary

Adds a durable Dependabot ignore rule so typescript semver-major updates are not re-raised until the lint toolchain supports the native port. This makes permanent the hold decided in #1014 (which landed @babel/parser 8 + the @supabase/supabase-js floor and deliberately kept TypeScript at 6) and supersedes the ad-hoc close of Dependabot #990.

Why: TypeScript 7 is the native (Go) port whose typescript package drops the classic programmatic compiler API (ts.createProgram/ts.transpileModule are undefined). typescript-eslint (latest 8.65.0, peer typescript: >=4.8.4 <6.1.0) and eslint-config-next don't support it, so a major bump hard-breaks the required type-aware lint gate. The repo already keeps a separate @typescript/typescript6 for compiler-API consumers.

    ignore:
      - dependency-name: "typescript"
        update-types: ["version-update:semver-major"]

Minor/patch TypeScript updates and all other dependencies are unaffected.

Verification

• Config-only change to .github/dependabot.yml; no source, tests, or lockfile touched.
• .github/dependabot.yml parses as valid YAML and the ignore entry has the correct Dependabot schema shape ([{dependency-name: "typescript", update-types: ["version-update:semver-major"]}]).
• npx prettier --check .github/dependabot.yml — clean.

Risk and rollout

• Risk: minimal — a scheduling/ignore preference for Dependabot only. No application, build, or dependency behavior changes.
• Rollback: remove the ignore block from .github/dependabot.yml.
• Provider or production effects: None.

Clinical Governance Preflight

Not applicable — no change to ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.

Notes

• Remove this rule once typescript-eslint + eslint-config-next publish releases whose typescript peer range includes 7.x — that's the single signal that TS7's native port is adoptable.

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated dependency update settings to defer major TypeScript upgrades.
  • Documented the current policy and exception for a separate TypeScript 6 setup.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

📝 Walkthrough

Walkthrough

Dependabot is configured to ignore semver-major updates for typescript, with comments documenting the repository’s current tooling compatibility constraint.

Changes

TypeScript Update Policy

Layer / File(s)	Summary
Block TypeScript major updates .github/dependabot.yml	Adds a Dependabot ignore rule for semver-major typescript updates and documents the related compatibility constraint.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: dependencies

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly states the Dependabot TypeScript major-bump ignore, which matches the PR's main change.
Description check	✅ Passed	The description follows the template and covers summary, verification, risk, rollback, and notes for this config-only change.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/resolve-dependency-prs-rmb9hv

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.