Skip to content

[Snyk] Upgrade @mdx-js/react from 3.0.1 to 3.1.1#289

Open
BekahHW wants to merge 1 commit intomainfrom
snyk-upgrade-0354bc98c3363a73f1e1081dda16906a
Open

[Snyk] Upgrade @mdx-js/react from 3.0.1 to 3.1.1#289
BekahHW wants to merge 1 commit intomainfrom
snyk-upgrade-0354bc98c3363a73f1e1081dda16906a

Conversation

@BekahHW
Copy link
Contributor

@BekahHW BekahHW commented Oct 9, 2025

snyk-top-banner

Snyk has created this PR to upgrade @mdx-js/react from 3.0.1 to 3.1.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: @mdx-js/react from @mdx-js/react GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade @mdx-js/react from 3.0.1 to 3.1.1
5e8eba5 
Snyk has created this PR to upgrade @mdx-js/react from 3.0.1 to 3.1.1.

See this package in npm:
@mdx-js/react

See this project in Snyk:
https://app.snyk.io/org/bekahhw/project/58f3bb64-0399-4f2b-8edb-1bfeda48f426?utm_source=github&utm_medium=referral&page=upgrade-pr
@BekahHW BekahHW requested a review from adiati98 as a code owner October 9, 2025 11:13
github-actions[bot]
github-actions bot reviewed Oct 9, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:

  • docs: correct typo in README
  • feat: implement dark mode"
  • fix: correct remove button behavior

Linting Errors

  • Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
  • No subject found

Watched Files

This pull request modifies specific files that require careful review by the maintainers.

Files Matched

  • package-lock.json
  • package.json

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

Reviewers

@github-actions github-actions[bot] github-actions[bot] left review comments

@adiati98 adiati98 Awaiting requested review from adiati98 adiati98 is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@BekahHW @snyk-bot