dependabot[bot] opened a new pull request, #71603: URL: https://github.com/apache/airflow/pull/71603
Bumps [openapi-merge-cli](https://github.com/robertmassaioli/openapi-merge) from 1.3.2 to 2.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/robertmassaioli/openapi-merge/releases";>openapi-merge-cli's releases</a>.</em></p> <blockquote> <h1>Release Notes — v2.0.2</h1> <p><strong>Covers:</strong> every change merged to <code>main</code> since the last published release, <code>[email protected]</code> / <code>[email protected]</code> (commit <code>bc232e4</code>, 2024-06-06), through <code>bbe4a5d</code> (2026-08-06).</p> <p><strong>Why 2.0.2, not 1.5.0:</strong> several changes below are behavior-breaking — most significantly, inputs that previously merged silently (while quietly losing data) now fail fast with a distinct exit code. <code>package.json</code> had already been bumped to <code>1.4.0</code> for the first of these (commit <code>1327cbf</code>) but never published; enough has landed since to warrant a major version instead of continuing to stack minors on an unpublished bump.</p> <p><strong>Why <code>.1</code>, not <code>.0</code>:</strong> the <code>v2.0.0</code> GitHub Release was cut first, but its publish run failed before anything reached npm (<code>bun publish</code> couldn't authenticate — see <code>scripts/publish-changed.sh</code>'s fix). The registry never saw a <code>2.0.0</code>, so this release goes out as <code>2.0.2</code> rather than reusing the tag.</p> <p>Both packages are version-locked and release together: <code>openapi-merge</code> and <code>openapi-merge-cli</code> both go to <code>2.0.2</code>.</p> <hr /> <h2>Breaking changes</h2> <ul> <li> <p><strong>Inputs' OpenAPI versions are now read and validated before any merging happens</strong> (issue <a href="https://redirect.github.com/robertmassaioli/openapi-merge/issues/113";>#113</a>, proposal <a href="https://github.com/robertmassaioli/openapi-merge/blob/HEAD/26-proposal-oas-phase1-version-checking.md";>26</a>). Previously the <code>openapi</code> field was never read: every input was merged under 3.0 assumptions, unrecognised constructs were silently dropped, and the output was stamped <code>3.0.3</code> regardless — with exit code <code>0</code>. Now:</p> <ul> <li>a missing, malformed, or unsupported <code>openapi</code> version fails with error type <code>unsupported-openapi-version</code>;</li> <li>inputs disagreeing on major.minor fails with <code>mixed-openapi-versions</code>;</li> <li>both surface as CLI exit code <code>9</code> (<code>ExitCode.ErrorOpenApiVersion</code>), distinct from the general <code>ErrorMerging</code> (<code>3</code>), because the remedy differs — the merge config isn't wrong, the inputs were never eligible to be merged together.</li> </ul> <p><strong>If your CI never noticed a previously-silent, data-losing merge, it will now fail there instead.</strong> That's the point of the change, but it is a behavior break worth testing before upgrading. There is no automatic upgrading of a mismatched input to a common version — that was investigated (proposal <a href="https://github.com/robertmassaioli/openapi-merge/blob/HEAD/25-proposal-mixed-version-inputs.md";>25</a>) and explicitly deferred; today's answer to a version mismatch is refuse, not auto-convert.</p> </li> <li> <p><strong>The CLI now propagates a non-zero exit code on every failure path</strong>, including previously-uncaught exceptions (issue <a href="https://redirect.github.com/robertmassaioli/openapi-merge/issues/92";>#92</a>).</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/robertmassaioli/openapi-merge/commits/v2.0.2";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~GitHub%20Actions";>GitHub Actions</a>, a new releaser for openapi-merge-cli since your current version.</p> </details> <details> <summary>Install script changes</summary> <p>This version modifies <code>prepare</code> script that runs during installation. Review the package contents before updating.</p> </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]
