Skip to content

build(deps): bump next-mdx-remote from 5.0.0 to 6.0.0 in /next-endpoint-ui#17

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-endpoint-ui/next-mdx-remote-6.0.0
Open

build(deps): bump next-mdx-remote from 5.0.0 to 6.0.0 in /next-endpoint-ui#17
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-endpoint-ui/next-mdx-remote-6.0.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 24, 2026

Bumps next-mdx-remote from 5.0.0 to 6.0.0.

Release notes

Sourced from next-mdx-remote's releases.

v6.0.0

Breaking/Major Changes

Changelog

Sourced from next-mdx-remote's changelog.

6.0.0

Breaking/Major Changes

  • Updated unist-util-remove to ^4.0.0
  • Introduced the parameters blockJS and blockDangerousJS that controls how JS in interpreted during compiling MDX. Both default to true for security reasons.
  • Updated the README to explain this change: hashicorp/next-mdx-remote#498.
Commits
Maintainer changes

This version was pushed to npm by rubennic, a new releaser for next-mdx-remote since your current version.


Dependabot compatibility score

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 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by cubic

Upgrade next-mdx-remote to 6.0.0 in next-endpoint-ui. v6 blocks JavaScript in MDX by default (blockJS, blockDangerousJS), which may change how MDX with inline JS renders.

  • Migration
    • If you rely on JS in MDX, set blockJS: false (and optionally blockDangerousJS: false) in your MDX compile/serialize options.
    • Review pages that render MDX and confirm components and expressions still render as expected.
    • Validate any custom remark/rehype plugins for compatibility with unist-util-remove v4.

Written for commit dde36ae. Summary will update on new commits.

Bumps [next-mdx-remote](https://github.com/hashicorp/next-mdx-remote) from 5.0.0 to 6.0.0.
- [Release notes](https://github.com/hashicorp/next-mdx-remote/releases)
- [Changelog](https://github.com/hashicorp/next-mdx-remote/blob/main/CHANGELOG.md)
- [Commits](hashicorp/next-mdx-remote@v5.0.0...v6.0.0)

---
updated-dependencies:
- dependency-name: next-mdx-remote
  dependency-version: 6.0.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Feb 24, 2026
Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 2 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="next-endpoint-ui/package.json">

<violation number="1" location="next-endpoint-ui/package.json:29">
P2: next-mdx-remote v6 blocks JavaScript expressions by default, but the MDX content relies on JSX expressions (e.g., `cols={2}`, `{" "}`) and MDXRemote isn’t configured to allow them. This upgrade will likely break rendering of docs pages unless you either remove JS expressions from MDX or pass `blockJS: false` for this trusted content.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

"lucide-react": "^0.554.0",
"next": "16.0.3",
"next-mdx-remote": "^5.0.0",
"next-mdx-remote": "^6.0.0",
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 24, 2026

Choose a reason for hiding this comment

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

P2: next-mdx-remote v6 blocks JavaScript expressions by default, but the MDX content relies on JSX expressions (e.g., cols={2}, {" "}) and MDXRemote isn’t configured to allow them. This upgrade will likely break rendering of docs pages unless you either remove JS expressions from MDX or pass blockJS: false for this trusted content.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At next-endpoint-ui/package.json, line 29:

<comment>next-mdx-remote v6 blocks JavaScript expressions by default, but the MDX content relies on JSX expressions (e.g., `cols={2}`, `{" "}`) and MDXRemote isn’t configured to allow them. This upgrade will likely break rendering of docs pages unless you either remove JS expressions from MDX or pass `blockJS: false` for this trusted content.</comment>

<file context>
@@ -26,7 +26,7 @@
     "lucide-react": "^0.554.0",
     "next": "16.0.3",
-    "next-mdx-remote": "^5.0.0",
+    "next-mdx-remote": "^6.0.0",
     "react": "19.2.0",
     "react-dom": "19.2.0",
</file context>
Fix with Cubic

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants