chore(deps): bump next-mdx-remote from 4.3.0 to 6.0.0#7243
chore(deps): bump next-mdx-remote from 4.3.0 to 6.0.0#7243dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
|
PR author is in the excluded authors list. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2d17717541
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "lodash": "^4.17.21", | ||
| "next": "^15.5.9", | ||
| "next-mdx-remote": "4.3.0", | ||
| "next-mdx-remote": "6.0.0", |
There was a problem hiding this comment.
Preserve MDX JS expressions when upgrading to v6
next-mdx-remote 6.0.0 changes JS handling defaults (blockJS/blockDangerousJS default to true), but extractMdx still calls serialize() without overriding those flags, while existing docs rely on MDX JS expressions (for example component props like labels={['npm', 'yarn', 'pnpm']} in apps/dev-portal-web/docs/ui/about.en.mdx). This can break server-side compilation/rendering of documentation pages after the dependency bump unless the serializer options are updated or docs are migrated away from JS expressions.
Useful? React with 👍 / 👎.
2d17717 to
14d2c17
Compare
14d2c17 to
99d0588
Compare
99d0588 to
7fb9704
Compare
7fb9704 to
97e2c31
Compare
97e2c31 to
268eba0
Compare
268eba0 to
bdd14e0
Compare
bdd14e0 to
6eaecba
Compare
6eaecba to
1c38f0b
Compare
1c38f0b to
b886475
Compare
b886475 to
434b6e0
Compare
434b6e0 to
a8b0680
Compare
a8b0680 to
52bdb7c
Compare
52bdb7c to
5a40d7d
Compare
5a40d7d to
d427847
Compare
Bumps [next-mdx-remote](https://github.com/hashicorp/next-mdx-remote) from 4.3.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@v4.3.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>
d427847 to
dd9ab4e
Compare
|



Bumps next-mdx-remote from 4.3.0 to 6.0.0.
Release notes
Sourced from next-mdx-remote's releases.
... (truncated)
Changelog
Sourced from next-mdx-remote's changelog.
Commits
f9aed8eUpdate CHANGELOG for version 6.0.04d527fdMerge pull request #498 from hashicorp/version-6.0.0ededdf5Get ready for 6.0.0 release17d6598chore: update issue templates0d8438ffix: add release script634b3b7Version Packages (#461)67a221fnext-mdx-remotev5 (#448)5ca1064Merge pull request #453 from hashicorp/compliance/add-headersa868874[COMPLIANCE] Add Copyright and License Headers5b97c4bchore: add issue templatesMaintainer changes
This version was pushed to npm by rubennic, a new releaser for next-mdx-remote since your current version.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.