dependabot[bot] opened a new pull request, #74263: URL: https://github.com/apache/airflow/pull/74263
Bumps [mermaid](https://github.com/mermaid-js/mermaid) from 11.17.2 to 12.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mermaid-js/mermaid/releases";>mermaid's releases</a>.</em></p> <blockquote> <h2>[email protected]</h2> <p><strong>Mermaid 12.0.0</strong> ships ELK as the bundled default layout engine, a new <code>redux-color</code> / <code>neo</code> default appearance, and two new diagram types: <a href="https://mermaid.ai/open-source/syntax/usecase.html";>UML use case diagrams</a>.</p> <p>This is a breaking release (ES2024, Safari 17.4+, Node 22.12+). Existing flowcharts, state and class diagrams will re-lay out and recolour; add <code>layout: dagre</code>, <code>theme: default</code> and <code>look: classic</code> to your config to keep the old look. Full changelog below.</p> <h3>Major Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/mermaid-js/mermaid/pull/8213";>#8213</a> <a href="https://github.com/mermaid-js/mermaid/commit/33442fddbf91852417ac2805afbd35aba0facbe1";><code>33442fd</code></a> Thanks <a href="https://github.com/aloisklink";><code>@aloisklink</code></a>! - chore!: require ES2024, Safari 17.4+, Node.JS v22.12+</p> <p>Mermaid is now built to target Safari 17.4+ and ES2024. If you need to support older browsers, you may need to polyfill or transpile mermaid.</p> <p>Safari 17.4+ has been chosen as the floor, as unlike Firefox/Chrome, older iOS devices don't get major Safari updates.</p> <p>Node.JS v22.12+ is also declared as requirement in our <code>package.json</code> files, but as mermaid requires a browser, this is mainly so we can use dependencies that also declare a Node.JS v22.12+ requirement, without causing issues for users when running <code>npm install</code>.</p> </li> <li> <p><a href="https://redirect.github.com/mermaid-js/mermaid/pull/8155";>#8155</a> <a href="https://github.com/mermaid-js/mermaid/commit/810893c660ada9e223297a38adcf65d4f4e211a7";><code>810893c</code></a> Thanks <a href="https://github.com/ashishjain0512";><code>@ashishjain0512</code></a>! - feat!: <strong>ELK is now bundled with mermaid and is the default layout algorithm.</strong></p> <p>ELK previously shipped as a separate <code>@mermaid-js/layout-elk</code> package that sites had to install and register. It is now part of mermaid itself and registered automatically, so <code>layout: elk</code> — and the <code>elk.stress</code>, <code>elk.force</code>, <code>elk.mrtree</code>, <code>elk.sporeOverlap</code>, <code>elk.box</code> and <code>elk.rectpacking</code> variants — work with no setup.</p> <p><strong>This changes how existing diagrams look.</strong> Flowchart, state, class, entity-relationship, requirement, use-case diagrams that do not specify a <code>layout</code> are now laid out by ELK instead of dagre. To keep the previous layout, set dagre explicitly:</p> <pre lang="yaml"><code>--- config: layout: dagre --- </code></pre> <p>or globally, <code>mermaid.initialize({ layout: 'dagre' })</code>.</p> <p>Mindmap is unchanged: it keeps laying out with cose-bilkent unless a layout is explicitly requested (in the tiny build, which ships neither ELK nor cose-bilkent, it falls back to dagre).</p> <p>Other notes:</p> <ul> <li>ELK is loaded as a separate chunk in the ESM builds, so it is only fetched when a diagram actually uses it. The single-file IIFE build (<code>mermaid.min.js</code>) inlines it and grows by roughly 500 kB gzipped.</li> <li>The <strong>tiny</strong> build deliberately omits ELK to stay small, and falls back to dagre for diagrams that ask for an ELK layout. Its size is unchanged.</li> <li><code>@mermaid-js/layout-elk</code> is no longer needed on normal builds — existing <code>mermaid.registerLayoutLoaders(elkLayouts)</code> calls keep working and can be removed. It is still published, and remains the way to add ELK to the tiny build.</li> <li><code>dist/mermaid.esm.min.mjs</code> now contains syntax that <code>es-module-lexer</code> (used by Vite) rejects with <code>content contains invalid JS syntax</code>. Bundler users are unaffected as long as they import the <code>mermaid</code> package specifier, which resolves to the core build; only builds that point Vite directly at that dist file need to switch to the package specifier or the core build.</li> <li>State diagrams now resolve their layout through the same registration check as every other diagram, so an unavailable layout falls back instead of failing to render.</li> </ul> <p>An unrecognised <code>theme</code> name now resolves to the default theme in name as well as in variables; previously the invalid name stayed in place while the default's variables were loaded, and every palette-aware stylesheet gates on the name. <code>theme: 'null'</code>, the documented way to disable the pre-defined themes, is unaffected. Note that <code>neo</code> paints node strokes with a gradient when the theme sets <code>useGradient</code>, which <code>base</code> does; setting a custom <code>nodeBorder</code> on <code>base</code> turns the gradient off.</p> </li> <li> <p><a href="https://redirect.github.com/mermaid-js/mermaid/pull/8211";>#8211</a> <a href="https://github.com/mermaid-js/mermaid/commit/a19bd085b6994e3c0b142a5e152559eef49935de";><code>a19bd08</code></a> Thanks <a href="https://github.com/ashishjain0512";><code>@ashishjain0512</code></a>! - <strong>Removed: the <code>defaultRenderer</code> option of the <code>flowchart</code>, <code>class</code> and <code>state</code> config sections.</strong></p> <p>Use the top-level <code>layout</code> option instead:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mermaid-js/mermaid/commit/98a0945418c76238f15df2afaddbba4272656c3b";><code>98a0945</code></a> Merge pull request <a href="https://redirect.github.com/mermaid-js/mermaid/issues/8237";>#8237</a> from mermaid-js/changeset-release/master</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/96be5640933281cea2a423edf82db51dbc75e4da";><code>96be564</code></a> Version Packages</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/dd65cfd479e95ee104e69d2c37e2ad227128343e";><code>dd65cfd</code></a> Merge pull request <a href="https://redirect.github.com/mermaid-js/mermaid/issues/8239";>#8239</a> from mermaid-js/bug/appearance-docs-release-version-...</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/e1cc7c2c024e42d38725a60b9a56c12dd8a13d84";><code>e1cc7c2</code></a> fix(tests): accept a released version in the appearance docs marker</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/8382837fd325296277a6523dd515ecdf1d54c6ae";><code>8382837</code></a> Merge pull request <a href="https://redirect.github.com/mermaid-js/mermaid/issues/8211";>#8211</a> from mermaid-js/release/12.0.0</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/8a903891e0de3323017e5a66912eacaccbda0574";><code>8a90389</code></a> ci: trigger a preview publish</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/01b8590f58186e772548a7ba8b42f0405a69f1c9";><code>01b8590</code></a> ci: attempt every preview package before failing the publish step</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/1997a2312994cd40283ce9af8faabfcbaa654af0";><code>1997a23</code></a> ci: record why the preview publish of layout-elk and tiny is refused</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/03040071acd9b166c18d0d869e3e8319b584de9a";><code>0304007</code></a> ci: drop --access public from the preview publish of layout-elk and tiny</li> <li><a href="https://github.com/mermaid-js/mermaid/commit/223be9293482c878a61448c52cf55082498a0198";><code>223be92</code></a> docs: capitalize Markdown in README tagline</li> <li>Additional commits viewable in <a href="https://github.com/mermaid-js/mermaid/compare/[email protected]@12.0.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
