Skip to content

[Snyk] Upgrade mjml from 5.0.0 to 5.4.0 - #803

Open
qbey wants to merge 1 commit into
mainfrom
snyk-upgrade-ef866cf9c55f75e5ccf43a247ec1d08d
Open

[Snyk] Upgrade mjml from 5.0.0 to 5.4.0#803
qbey wants to merge 1 commit into
mainfrom
snyk-upgrade-ef866cf9c55f75e5ccf43a247ec1d08d

Conversation

@qbey

@qbey qbey commented Aug 8, 2026

Copy link
Copy Markdown
Member

snyk-top-banner

Snyk has created this PR to upgrade mjml from 5.0.0 to 5.4.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 10 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PICOMATCH-15765511
435 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-PICOMATCH-15765513
435 No Known Exploit

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

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

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

For more information:

@qbey

qbey commented Aug 8, 2026

Copy link
Copy Markdown
Member Author

Merge Risk: Medium

This upgrade from mjml 5.0.0 to 5.4.0 contains a security-driven breaking change and changes to the output formatting.

Breaking Change: mj-include is now opt-in
To address a security vulnerability (GHSA-45h5-66jx-r2wf), version 5.1.0 changed the default behavior of <mj-include>. It is now disabled by default.

Recommendation: If you use <mj-include>, you must now explicitly enable it in your configuration. This is a necessary action to prevent your builds from failing or producing incorrect output.

Behavioral Change: Output Formatting

  • v5.1.0: The HTML beautification engine was changed to Biome.
  • v5.2.0: The engine was reverted back to js-beautify to address performance and stability issues introduced in the previous change.

These changes may cause variations in the generated HTML output. It is recommended to review the rendered output to ensure it has not negatively impacted your emails.

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

@sonarqubecloud

sonarqubecloud Bot commented Aug 8, 2026

Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants