Skip to content

chore(deps): update shiki monorepo to v4 (major)#2419

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-shiki-monorepo
Open

chore(deps): update shiki monorepo to v4 (major)#2419
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-shiki-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2026

This PR contains the following updates:

Package Change Age Confidence
@shikijs/monaco (source) ^3.21.0^4.0.0 age confidence
@shikijs/vitepress-twoslash (source) ^3^4.0.0 age confidence

Release Notes

shikijs/shiki (@​shikijs/monaco)

v4.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
    View changes on GitHub

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-shiki-monorepo branch from 2f6ff29 to b1fa1e2 Compare March 2, 2026 07:44
@renejeglinsky renejeglinsky requested review from Akatuoro and chgeo March 2, 2026 13:08
Copy link
Contributor

@Akatuoro Akatuoro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 live cql snippets are still highlighted and without layout shift

@renejeglinsky
Copy link
Contributor

I'm not sure how to solve the build error.

@renovate renovate bot force-pushed the renovate/major-shiki-monorepo branch from 9cbb4d6 to 82ca66d Compare March 10, 2026 17:32
@Akatuoro
Copy link
Contributor

I'm not sure how to solve the build error.

That's our internal build and the package lock is not matching -> create a branch with the same name and an updated package-lock.json in the internal repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants