chore: update testutils

[UziTech]

Description

Update @markedjs/testutils to version 17.0.1-2

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

@UziTech is attempting to deploy a commit to the MarkedJS Team on Vercel.

A member of the Team first needs to authorize it.

[gemini-code-assist]

Summary of Changes

Hello @UziTech, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a routine maintenance task: updating the @markedjs/testutils package to its latest version. This ensures that the project benefits from the most recent features, bug fixes, and security enhancements provided by the testing utilities and their underlying dependencies. The update also aligns the project with newer Node.js environment standards.

Highlights

• Dependency Update: The @markedjs/testutils package has been updated from version 15.0.11-0 to 17.0.1-2.
• Transitive Dependency Updates: This update includes new versions for several transitive dependencies, such as @markedjs/html-differ (to 5.0.4), marked (to 17.0.1), parse5-sax-parser (to 8.0.0), and chalk (to 5.6.2).
• Node.js Version Requirement: The minimum Node.js engine requirement for the marked package (used by testutils) has been raised from >= 18 to >= 20.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[vercel]

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

Project	Deployment	Review	Updated (UTC)
marked-website	Ready	Preview, Comment	Dec 30, 2025 9:44pm

[gemini-code-assist]

Code Review

This pull request updates the @markedjs/testutils dev dependency from 15.0.11-0 to 17.0.1-2. This is a major version bump which also updates several transitive dependencies, most notably marked itself to 17.0.1. The changes are confined to package.json and package-lock.json and appear correct and consistent. Since no code changes were necessary to accommodate this major version bump, it suggests the new version is API-compatible. Assuming CI passes, this change is good to go.