[Snyk] Security upgrade markdownlint-cli from 0.31.1 to 0.39.0

[MaxMood96]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/scripts/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Inefficient Algorithmic Complexity SNYK-JS-LINKIFYIT-17901217

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[MaxMood96]

This upgrade of markdownlint-cli contains updates that drop support for an end-of-life Node.js version and introduce minor behavioral changes.

Key Changes:

• Node.js Version: Starting with v0.38.0, this package relies on an updated version of the markdownlint library which removes support for the end-of-life Node.js version 18. [3]
• CLI Behavior: Version 0.34.0 improved how directories are handled by the --ignore flag, causing it to ignore all files within the specified directory. [3]
• New Features: Support for TOML configuration files was added in v0.34.0. [3]

Recommendation:
Ensure your production environment and CI/CD pipelines are running a supported version of Node.js (v20 or newer). Review any usage of the --ignore flag with directories to confirm it aligns with the updated behavior.

Source: Release notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @snyk-bot, @MaxMood96, @mergify.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: snyk-bot, MaxMood96, mergify.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.