Update dependency shiki to v0.14.7
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| shiki (source) | 0.14.5 -> 0.14.7 |
Release Notes
shikijs/shiki (shiki)
v0.14.7
🙌 Contributions
- doc: fix typo | #544 | @Seven-Y-Q-Guo
- feat: Add
nushellgrammar | #522 | @hustcer - feat: add
wlalias forwolfram| #535 | @stone-zeng
v0.14.6
🚀 Features & Fixes
- fix: update razor grammar source
- fix: update kotlin language source
- fix: update vue syntax path
🙌 Contributions
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| ding-one | ❌ Failed (Inspect) | Jan 28, 2024 6:11am |
Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword
link(e.g. "Link T-123").💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.
PR Summary
-
Updated
shikidependency version inpackage.jsonThe version of theshikisoftware component in thepackage.jsonfile has been updated, moving from0.14.5to a newer version,0.14.7. This update can bring improvements, bug fixes, and possibly new features from theshikiproject. -
Revised lock file to match
shikiversion upgrade In line with the upgrade made in thepackage.json, the lock file (pnpm-lock.yaml) has also been updated to reflect the sameshikiversion change. This is essential to ensure all parts of our project are in sync and referencing the correct version ofshiki. This helps avoid potential conflicts and issues that could arise if different parts of our project were using different versions.