Bump react-markdown from 8.0.7 to 9.0.3

[dependabot]

Bumps react-markdown from 8.0.7 to 9.0.3.

Release notes

Sourced from react-markdown's releases.

9.0.3

(same as 9.0.2 but now with d.ts files)

Full Changelog: remarkjs/react-markdown@9.0.2...9.0.3

9.0.2

Types

• b151a90 Fix types for React 19 by @​remcohaszing in remarkjs/react-markdown#879
• 6962af7 Add declaration maps
• aa5933b Refactor to use @import to import types by @​remcohaszing in remarkjs/react-markdown#836

Miscellaneous

• 9eb589e Fix typo in changelog by @​NicholasWilsonDEV in remarkjs/react-markdown#874
• 515bf19 Fix typo by @​deep-lyra in remarkjs/react-markdown#868

Full Changelog: remarkjs/react-markdown@9.0.1...9.0.2

9.0.1

• d8e3787 Fix double encoding in new url transform
• 55d8d83 Refactor docs to use createRoot

Full Changelog: remarkjs/react-markdown@9.0.0...9.0.1

9.0.0

Change

• b67d714 Change to require Node.js 16 migrate: update too
• ec2b134 Change to require React 18 migrate: update too
• bf5824f Change to use exports migrate: don’t use private APIs
• c383a45 Update @types/hast, utilities, plugins, etc migrate: update too
• eca5e6b 08ead9e Replace transformImageUri, transformLinkUri w/ urlTransform migrate: see Add urlTransform
• de29396 Remove linkTarget option by @​galabra in remarkjs/react-markdown#762 migrate: see Remove linkTarget
• 4346276 Remove support for passing custom props to components migrate: see Remove includeElementIndex, Remove rawSourcePos, Remove sourcePos, Remove extra props passed to certain components
• c0dfbd6 Remove UMD bundle from package migrate: use esm.sh or a CDN or so
• e12b5e9 Remove prop-types

... (truncated)

Changelog

Sourced from react-markdown's changelog.

Changelog

All notable changes will be documented in this file.

9.0.0 - 2023-09-27

• b67d714 Change to require Node.js 16
  migrate: update too
• ec2b134 Change to require React 18
  migrate: update too
• bf5824f Change to use exports
  migrate: don’t use private APIs
• c383a45 Update @types/hast, utilities, plugins, etc
  migrate: update too
• eca5e6b 08ead9e Replace transformImageUri, transformLinkUri w/ urlTransform
  migrate: see “Add urlTransform” below
• de29396 Remove linkTarget option
  migrate: see “Remove linkTarget” below
• 4346276 Remove support for passing custom props to components
  migrate: see “Remove includeElementIndex”, “Remove rawSourcePos”, “Remove sourcePos”, “Remove extra props passed to certain components” below
• c0dfbd6 Remove UMD bundle from package
  migrate: use esm.sh or a CDN or so
• e12b5e9 Remove prop-types
  migrate: use TypeScript
• 4eb7aa0 Change to throw errors for removed props
  migrate: don’t pass options that don’t do things
• 8aabf74 Change to improve error messages
  migrate: expect better messages

Add urlTransform

The transformImageUri and transformLinkUri were removed. Having two functions is a bit much, particularly because there are more URLs you might want to change (or which might be unsafe so we make them safe). And their name and APIs were a bit weird. You can use the new urlTransform prop instead to change all your URLs.

... (truncated)

Commits

• aed0010 9.0.3
• 40c097e 9.0.2
• 2c6ffe8 Refactor .gitignore
• b664ac4 Update Actions
• e686551 Update dev-dependencies
• b151a90 Fix types for React 19
• 27d3949 Separate all typedefs into their own JSDoc blocks (#878)
• 9eb589e Fix typo in changelog
• 515bf19 Fix typo
• a7ca8ed Refactor .editorconfig
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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

Upgrade react-markdown to version 9.0.3.

New Features:

• Add support for the new urlTransform prop to transform URLs.

Enhancements:

• Upgrade react-markdown to v9 which requires React 18 and Node.js 16.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates react-markdown from version 8.0.7 to 9.0.3. This includes several important changes such as requiring Node.js 16, React 18, removing the UMD bundle, removing the linkTarget option, and replacing transformImageUri and transformLinkUri with urlTransform.

Class diagram showing changes to react-markdown API

classDiagram
    class ReactMarkdown {
        -urlTransform(url: string, type: string, defaultTransform: function)
    }
    note for ReactMarkdown "Breaking changes in v9.0.0:
    - Removed: transformImageUri
    - Removed: transformLinkUri
    - Removed: linkTarget
    - Removed: prop-types
    - Added: urlTransform"

Loading

File-Level Changes

Change	Details	Files
Updated the react-markdown dependency	Bumped react-markdown from 8.0.7 to 9.0.3 in package.json Updated yarn.lock to reflect the new react-markdown 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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Jan 15 2025 to showcase some of the refinements we've made.

🪧 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!

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 4a1f67a)

Action: deploy-preview

Failed stage: Deploy Project Artifacts to Vercel [❌]

Failure summary: The build failed due to a TypeScript type error in ./app/components/markdown.tsx. Specifically: There's a type mismatch in the remarkPlugins prop of the ReactMarkdown component The error occurs because the type (options?: void | Options | undefined) => void | Transformer<Root, Root> is not assignable to type Pluggable The error is on line 277 where [RemarkMath, RemarkGfm, RemarkBreaks] is being passed as remarkPlugins

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 646: 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 647: 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 648: ./app/components/realtime-chat/realtime-chat.tsx 649: 119:6 Warning: React Hook useCallback has a missing dependency: 'startResponseListener'. Either include it or remove the dependency array. react-hooks/exhaustive-deps 650: 270:6 Warning: React Hook useCallback has a missing dependency: 'handleInputAudio'. Either include it or remove the dependency array. react-hooks/exhaustive-deps 651: ./app/components/sd/sd.tsx 652: 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 653: info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules 654: Failed to compile. 655: ./app/components/markdown.tsx:277:35 656: Type error: Type '(options?: void | Options | undefined) => void | Transformer<Root, Root>' is not assignable to type 'Pluggable'. ... 666: �[0m �[90m 275 |�[39m �[36mreturn�[39m (�[0m 667: �[0m �[90m 276 |�[39m �[33m<�[39m�[33mReactMarkdown�[39m�[0m 668: �[0m�[31m�[1m>�[22m�[39m�[90m 277 |�[39m remarkPlugins�[33m=�[39m{[�[33mRemarkMath�[39m�[33m,�[39m �[33mRemarkGfm�[39m�[33m,�[39m �[33mRemarkBreaks�[39m]}�[0m 669: �[0m �[90m |�[39m �[31m�[1m^�[22m�[39m�[0m 670: �[0m �[90m 278 |�[39m rehypePlugins�[33m=�[39m{[�[0m 671: �[0m �[90m 279 |�[39m �[33mRehypeKatex�[39m�[33m,�[39m�[0m 672: �[0m �[90m 280 |�[39m [�[0m 673: Static worker exited with code: 1 and signal: null 674: error Command failed with exit code 1. 675: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 676: Error: Command "yarn run build" exited with 1 677: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.