Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade next-mdx-remote from 2.1.0 to 2.1.4 #35

Closed

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade next-mdx-remote from 2.1.0 to 2.1.4.

merge advice
ℹ️ 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 5 versions ahead of your current version.
  • The recommended version was released 9 months ago, on 2021-04-12.
Release notes
Package name: next-mdx-remote
  • 2.1.4 - 2021-04-12

    Previously, the peer dependency range for this library was very tight and cut off at react 17.0.1, so you'd get errors with the most recent react version. Now, it's a lot looser and will accept anything between react v16 and v18. Apologies for the annoyance!

    This release also comes with a number of wonderful additions to the documentation, thanks to those who contributed!

    Commit Log

    • Add circleci config: 7f128a4
    • Fix typo in README: 7fbc1ee
    • Merge pull request #109 from Hocdoc/patch-1: f775df6
    • Add example of replacing HTML tags as well: #113
    • Loosen react peer dependency semver range: 528bcbf

    Credits

    Huge thanks to @ eric-burel for helping!

  • 2.1.4-xdm.0 - 2021-02-17

    2.1.4-xdm.0

  • 2.1.3 - 2021-01-22

    Fixes type imports so they work when consumed (#99)

    Huge thanks to @ BRKalow for this fix!

  • 2.1.2 - 2021-01-21

    Fixes typings for remark plugins (#96)

  • 2.1.1 - 2021-01-07

    Fixes typing for the MdxRemote.Components type, and fixes a couple dependencies. Thanks to @ MatthewCaseres for filing the typescript issue!

    Patches

    • Fix component typings: #95
    • Bump ini from 1.3.5 to 1.3.8: #92
    • Bump dot-prop from 4.2.0 to 4.2.1: #93
  • 2.1.0 - 2021-01-06

    This release adds support for wrapping the MDX content with custom providers! You can now pass a provider to both renderToString and hydrate:

    renderToString(source, { provider: { component: MyProvider, props: { my: 'prop' } } });
    hydrate(mdxSource, { provider: { component: MyProvider, props: { my: 'prop' } } });

    Check out the README section on using providers for more information.

    Big thanks to all who contributed to this release, either through direct contributions or testing:

    • @ devrsi0n for getting the custom provider work started
    • @ ynnoj for testing out the custom provider functionality in his project and identifying a bug in the initial implementation!
    • @ marcofranssen for updating our react peer dependencies

    And a thanks to everyone who participated in the discussion, we appreciate all of your contributions! 🙏

    Minor Changes

    • Support custom Providers (#35)
    • Fix peer dependencies to include react 17.0.1 (#91)
from next-mdx-remote GitHub release notes
Commit messages
Package name: next-mdx-remote

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@github-actions
Copy link

This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions.

@github-actions
Copy link

Closing due to inactivity. If you feel this was a mistake or you wish to re-open at any time in the future, please leave a comment and it will be re-surfaced for the maintainers to review.

@github-actions github-actions bot closed this Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant