[Snyk] Upgrade @c15t/react from 1.4.4 to 1.6.1

[sestinj]

Snyk has created this PR to upgrade @c15t/react from 1.4.4 to 1.6.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 13 versions ahead of your current version.

• The recommended version was released 2 months ago.

Release notes

Package name: @c15t/react

• 1.6.1 - 2025-09-18
• 1.6.0 - 2025-09-10
• 1.5.1-canary-20250909182627 - 2025-09-09
• 1.5.0 - 2025-07-30
• 1.5.0-canary-20250908140135 - 2025-09-08
• 1.5.0-canary-20250904090836 - 2025-09-04
• 1.5.0-canary-20250902132553 - 2025-09-02
• 1.5.0-canary-20250813173036 - 2025-08-13
• 1.5.0-canary-20250813161712 - 2025-08-13
• 1.5.0-canary-20250722151007 - 2025-07-22
• 1.5.0-canary-20250722133547 - 2025-07-22
• 1.5.0-canary-20250722085128 - 2025-07-22
• 1.5.0-canary-20250709081316 - 2025-07-09
• 1.4.4 - 2025-07-17

from @c15t/react GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Summary by cubic

Upgraded @c15t/react from 1.4.4 to 1.6.1 in the docs package to pick up recent fixes and improvements. This keeps the dependency current.

• Dependencies
  • Bumped @c15t/react to ^1.6.1 in docs/package.json.
  • Updated docs/package-lock.json.
  • Verify the docs build and UI in preview.

^{Written for commit 835b9c4. Summary will update automatically on new commits.}

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.

---

[cubic-dev-ai]

No issues found across 2 files