Bump rehype-highlight from 6.0.0 to 7.0.2

[dependabot]

Bumps rehype-highlight from 6.0.0 to 7.0.2.

Release notes

Sourced from rehype-highlight's releases.

7.0.2

Fix

• 5c3b277 Fix multiple codes in a pre

Full Changelog: rehypejs/rehype-highlight@7.0.1...7.0.2

7.0.1

Fix

• 8fbc0eb Fix to prefer no-highlight class over language-* class

Types

• f74755f Add declaration maps
• 28a031f Refactor to use @import

Docs

• a2d4dc3 Add HTML, CSS sections to readme
• 67eeb3a Add example, links to rehype-highlight-code-lines
• 3c2d9e0 Add references to rehype-starry-night in docs

Full Changelog: rehypejs/rehype-highlight@7.0.0...7.0.1

7.0.0

Change

• d72c765 Update lowlight migrate: if you pass languages, make sure the spread in common from lowlight: .use(rehypeHighlight, {...common, ...otherLanguages})
• b057174 Update @types/hast, unified, utilities, etc migrate: update too
• 72fe488 Change to require Node.js 16 migrate: update too
• d2fc56d Change to use exports migrate: don’t use private APIs
• dc3823d Remove ignoreMissing option, make it default migrate: remove ignoreMissing, expect warnings on the file instead

Misc

• d05e002 Fix broken import in example by @​rhysd in rehypejs/rehype-highlight#24

Full Changelog: rehypejs/rehype-highlight@6.0.0...7.0.0

Commits

• 86a5e9b 7.0.2
• ff5d9df Refactor tests
• 5c3b277 Fix multiple codes in a pre
• 093fed2 Refactor example
• 6275528 Refactor package.json
• 6a63f71 Update tests for changes in lowlight
• 36727b6 Update dev-dependencies
• 241ced9 Update Actions
• 79b5c4f 7.0.1
• a2d4dc3 Add HTML, CSS sections to readme
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Build:

• Update rehype-highlight dependency from version 6.0.0 to 7.0.2 in package.json.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the version of the 'rehype-highlight' dependency from 6.0.0 to 7.0.2 and updates the associated lock file, ensuring that the latest fixes and improvements from the dependency are applied.

Flow Diagram for rehype-highlight Dependency Update Process

flowchart TD
    A[Start] --> B[Detect outdated dependency: rehype-highlight 6.0.0]
    B --> C[Update package.json to 7.0.2]
    C --> D[Update yarn.lock accordingly]
    D --> E[Run tests and validations]
    E --> F[Commit and merge PR]

Loading

File-Level Changes

Change	Details	Files
Updated dependency version for rehype-highlight	Changed the version number from 6.0.0 to 7.0.2 in the dependency list Updated the lock file to reflect the new dependency version	package.json yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: deploy-preview

Failed stage: Deploy Project Artifacts to Vercel [❌]

Failure summary: The action failed during the build process due to a TypeScript type error in ./app/components/markdown.tsx: The RehypeHighlight plugin is not properly typed and is incompatible with the expected Plugin type Specifically, the error occurs on line 281 where the return type of the plugin doesn't match the expected Plugin interface Additional ESLint warnings were present but were not the cause of the build failure

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 653: 1938:29 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element 654: 1956:35 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element 655: ./app/components/realtime-chat/realtime-chat.tsx 656: 119:6 Warning: React Hook useCallback has a missing dependency: 'startResponseListener'. Either include it or remove the dependency array. react-hooks/exhaustive-deps 657: 270:6 Warning: React Hook useCallback has a missing dependency: 'handleInputAudio'. Either include it or remove the dependency array. react-hooks/exhaustive-deps 658: ./app/components/sd/sd.tsx 659: 165:25 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element 660: info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules 661: Failed to compile. 662: ./app/components/markdown.tsx:281:11 663: Type error: Type '(options?: Readonly<Options> | null | undefined) => (tree: Root, file: VFile) => undefined' is not assignable to type 'Plugin<any[], any, any>'. ... 671: �[0m �[90m 279 |�[39m �[33mRehypeKatex�[39m�[33m,�[39m�[0m 672: �[0m �[90m 280 |�[39m [�[0m 673: �[0m�[31m�[1m>�[22m�[39m�[90m 281 |�[39m �[33mRehypeHighlight�[39m�[33m,�[39m�[0m 674: �[0m �[90m |�[39m �[31m�[1m^�[22m�[39m�[0m 675: �[0m �[90m 282 |�[39m {�[0m 676: �[0m �[90m 283 |�[39m detect�[33m:�[39m �[36mfalse�[39m�[33m,�[39m�[0m 677: �[0m �[90m 284 |�[39m ignoreMissing�[33m:�[39m �[36mtrue�[39m�[33m,�[39m�[0m 678: Static worker exited with code: 1 and signal: null 679: error Command failed with exit code 1. 680: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 681: Error: Command "yarn run build" exited with 1 682: ##[error]Process completed with exit code 1.