fix: allow TypeScript 6 and 7 as peer dependencies for react-shepherd

[RobbieTheWagner]

react-shepherd declared typescript@^5.0.0 as a peer dependency, which made npm install fail with a peer-resolution conflict for consumers on TypeScript 6 (npm strict peer deps). This relaxes the range to ^5.0.0 || ^6.0.0 || ^7.0.0.

Closes #3445

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Expanded TypeScript compatibility for the React package to support versions 5, 6, and 7.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
shepherd-docs	Ready	Preview	Aug 10, 2026 2:13am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
shepherd-landing	Skipped		Aug 10, 2026 2:13am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bccb948c-698c-402f-863b-8014050b5550

📥 Commits

Reviewing files that changed from the base of the PR and between de542f0 and d2df456.

📒 Files selected for processing (1)

• packages/react/package.json

---

📝 Walkthrough

Walkthrough

The React package expands its TypeScript peer dependency from version 5 to versions 5, 6, and 7.

Changes

TypeScript peer dependency

Layer / File(s)	Summary
Expand TypeScript peer range packages/react/package.json	The TypeScript peer dependency now accepts ^5.0.0, ^6.0.0, or ^7.0.0.

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

Suggested labels: enhancement

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: allowing TypeScript 6 and 7 as peer dependencies for react-shepherd.
Linked Issues check	✅ Passed	The change updates the TypeScript peer dependency range to include TypeScript 6, resolving the peer-resolution conflict described in issue #3445.
Out of Scope Changes check	✅ Passed	The pull request contains one package metadata change directly related to the linked issue and stated objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch relax-ts-peer-dep

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.