chore(security): bump next-mdx-remote to 6.0.0

[abel-castro]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
abelcastro-dev-next	Ready	Preview, Comment	Feb 15, 2026 5:03am

[Copilot]

Pull request overview

This PR bumps the next-mdx-remote package from version 5.0.0 to 6.0.0 as a security update. The upgrade includes updates to transitive dependencies in the unist utility packages, modernizing the dependency tree to use newer versions of these utilities.

Changes:

• Updated next-mdx-remote from ^5.0.0 to 6.0.0 (with pinned version)
• Updated transitive dependencies: unist-util-remove (3.1.1 → 4.0.0) and unist-util-visit (5.0.0 → 5.1.0)
• Removed obsolete v5 unist utility dependencies that are no longer needed

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updated next-mdx-remote dependency from ^5.0.0 to pinned 6.0.0
pnpm-lock.yaml	Updated lockfile with new next-mdx-remote version, transitive dependency updates, and removed obsolete v5 unist utilities

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The version specifier for next-mdx-remote has been changed from a caret range (^5.0.0) to a pinned version (6.0.0). This is inconsistent with the versioning strategy used for nearly all other dependencies in this project, which use caret ranges to allow automatic minor and patch updates. Consider using ^6.0.0 instead to maintain consistency and allow for automatic patch and minor version updates while preventing breaking major version changes.

Suggested change

	"next-mdx-remote": "6.0.0",
	"next-mdx-remote": "^6.0.0",

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.