chore(deps): update shiki to ^3.12.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
shiki (source)	^3.11.0 -> ^3.12.2

---

Release Notes

shikijs/shiki (shiki)

v3.12.2

Compare Source

   🐞 Bug Fixes

• twoslash: Fix onTwoslashError return value handling  -  by @​Karibash in #​1070 (e86b0)

    View changes on GitHub

v3.12.1

Compare Source

No significant changes

    View changes on GitHub

v3.12.0

Compare Source

   🚀 Features

• vitepress-twoslash:
  • Improve UX for option customization  -  by @​9romise in #​1066 (e3cfd)
  • Twoslash inline type cache for markdown  -  by @​serkodev and @​antfu in #​1063 (dc7fb)

   🐞 Bug Fixes

• remove-notation-escape: Correct escape sequence  -  by @​sor4chi in #​1065 (22d0c)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) in timezone America/New_York, 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.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
react-shiki	Ready	Preview	Comment	Sep 9, 2025 6:13am

[changeset-bot]

🦋 Changeset detected

Latest commit: 2452b2e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
react-shiki	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[claude]

Claude finished @renovate[bot]'s task —— View job

---

✅ Shiki Dependency Update Review Complete

Todo List:

• Read repository guidelines (CLAUDE.md) - No CLAUDE.md found
• Review changed files and dependency update scope
• Analyze shiki changelog for breaking changes or API impacts
• Check if react-shiki code uses affected features
• Verify changeset is appropriate
• Assess if documentation updates are needed
• Provide comprehensive review feedback

📋 Review Summary

This is a clean and safe dependency update with all necessary components properly handled.

✅ Requirements Met

✅ Changeset Included

• Proper changeset file added: .changeset/renovate-f843529.md
• Correctly set as patch version bump (appropriate for dependency update)
• Clear description: "Updated dependency shiki to ^3.12.2"

✅ No Documentation Updates Needed

• No API surface changes - This is a dependency update only
• Shiki 3.11.0 → 3.12.2 maintains full backward compatibility
• No breaking changes affecting react-shiki's public API

✅ Clean Architecture

• Dependency update properly isolated to package.json and pnpm-lock.yaml
• No source code changes required - excellent encapsulation

🔍 Impact Analysis

Shiki Changes (3.11.0 → 3.12.2):

• v3.12.2: Bug fix in onTwoslashError return value handling
• v3.12.1: No significant changes
• v3.12.0:
  • VitePress-TwoSlash UX improvements
  • TwoSlash inline type cache
  • Fix for escape sequence in remove-notation-escape

✅ Compatibility Assessment:

• No Breaking Changes - All changes are additive or internal fixes
• No API Changes affecting react-shiki's usage of Shiki core APIs
• react-shiki uses codeToHast() and codeToHtml() which remain unchanged
• Transformer system compatibility maintained

🧪 Code Quality Assessment

✅ Best Practices Followed:

• Semantic Versioning: Patch bump for dependency update ✓
• Automated Updates: Renovate PR with proper metadata ✓
• Lock File: pnpm-lock.yaml properly updated ✓
• Changeset: Appropriate version and description ✓

🔒 Security & Performance:

• No Security Concerns - Minor version update from trusted source
• Performance: Potential improvements from bug fixes, no regressions expected
• Bundle Size: Minimal impact (likely neutral or slight improvement)

🎯 Recommendation

✅ APPROVE AND MERGE

This is a textbook example of a well-managed dependency update:

• All required components present and correct
• No breaking changes or API surface impacts
• Clean, isolated change with proper documentation
• Low risk, high benefit update

🚀 Next Steps

1. Merge when ready - No additional changes needed
2. Consider running tests locally if desired for extra confidence
3. Monitor the Vercel deployment to ensure everything works as expected