dependabot[bot] opened a new pull request, #73484:
URL: https://github.com/apache/airflow/pull/73484

   Bumps 
[json-schema-to-typescript](https://github.com/bcherny/json-schema-to-typescript)
 from 15.0.4 to 16.0.0.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/bcherny/json-schema-to-typescript/blob/master/CHANGELOG.md";>json-schema-to-typescript's
 changelog</a>.</em></p>
   <blockquote>
   <h2>16.0.0</h2>
   <p>This release collects the fixes and small features merged since 15.0.4. 
Several of them correct types that were previously emitted wrong, so existing 
schemas may generate different output; hence the major version.</p>
   <p>New:</p>
   <ul>
   <li>e3c7776 Feat: Support OpenAPI 3.0 <code>nullable: true</code>, including 
next to a <code>$ref</code>; such schemas now emit <code>T | null</code> (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/755";>#755</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/410";>#410</a>)</li>
   <li>ab31f41 Feat: Support draft-3 / Swagger 2 property-level <code>required: 
true</code>; such properties are now emitted as required (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/756";>#756</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/440";>#440</a>,
 <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/6";>#6</a>)</li>
   <li>111c187 Feat: Resolve draft-07 named-anchor <code>$ref</code>s 
(<code>&quot;#name&quot;</code> matching a sibling <code>$id: 
&quot;#name&quot;</code>) instead of crashing (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/744";>#744</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/220";>#220</a>)</li>
   </ul>
   <p>May change emitted types for existing schemas:</p>
   <ul>
   <li>efceb64 Bugfix: Multiple <code>patternProperties</code> (or 
<code>patternProperties</code> with <code>additionalProperties: false</code>) 
are folded into one index signature typed as the union of their value types, 
instead of being dropped (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/754";>#754</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/160";>#160</a>,
 <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/315";>#315</a>)</li>
   <li>b84b3da Bugfix: <code>allOf</code> members made up only of unsupported 
keywords (eg. <code>if</code>/<code>then</code>, <code>not</code>) no longer 
add a stray <code>{[k: string]: unknown}</code> to the intersection (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/743";>#743</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/369";>#369</a>)</li>
   <li>d8618e5 Bugfix: <code>properties</code>/<code>patternProperties</code> 
on a nested schema were dropped when combined with 
<code>oneOf</code>/<code>anyOf</code>/<code>allOf</code>; they are now 
intersected with the compound type (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/708";>#708</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/630";>#630</a>)</li>
   <li>4eee0f1 Bugfix: <code>$ref</code>s to definitions with dotted names (eg. 
<code>#/definitions/v1.ManagedFieldsEntry</code>) were truncated at the first 
dot (<code>V1</code>); the full name is now used 
(<code>V1ManagedFieldsEntry</code>) (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/705";>#705</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/645";>#645</a>)</li>
   <li>7a3dd8e Bugfix: Nested arrays with 
<code>minItems</code>/<code>maxItems</code> are capped by the cumulative 
product of their bounds against <code>maxItems</code>, falling back to an 
unbounded array instead of hanging or emitting enormous tuple unions (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/703";>#703</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/690";>#690</a>)</li>
   <li>34a692c Bugfix: <code>type: null</code> (the JSON null value) is treated 
as <code>type: &quot;null&quot;</code> instead of as an untyped object (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/702";>#702</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/667";>#667</a>)</li>
   <li>0f9d309 Bugfix: <code>unreachableDefinitions</code> now declares 
definitions even when <code>declareExternallyReferenced</code> is off (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/706";>#706</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/652";>#652</a>)</li>
   <li>1900e1f Bugfix: With <code>inferStringEnumKeysFromValues</code>, a 
<code>const</code> is emitted as a literal type again rather than a 
single-member enum (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/701";>#701</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/666";>#666</a>)</li>
   <li>606e359 Bugfix: A schema with an array <code>type</code> and 
<code>properties</code> (eg. <code>type: ['object', 'null']</code>) at the root 
or as an untitled definition compiled to <code>A &amp; (A | null)</code>, 
making the non-object members unreachable; it now emits <code>A | null</code> 
(<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/753";>#753</a>,
 supersedes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/672";>#672</a>)</li>
   <li>c73ea75 Bugfix: An empty schema inside <code>allOf</code> (eg. 
<code>allOf: [{$ref: '#/definitions/User'}, {}]</code>) collapsed the whole 
intersection to <code>unknown</code>; the empty member is now dropped and 
<code>User</code> is kept (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/752";>#752</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/654";>#654</a>)</li>
   <li>9c50776 Bugfix: The <code>description</code> of an inline 
<code>items</code> schema is no longer dropped; it is added to the JSDoc of the 
array's declaration as an <code>Items: ...</code> paragraph (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/751";>#751</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/660";>#660</a>)</li>
   </ul>
   <p>Fixes for crashes and output that did not compile:</p>
   <ul>
   <li>b25c768 Bugfix: A root-level <code>$ref</code> to a definition that is 
itself only a <code>$ref</code> no longer crashes with &quot;Refs should have 
been resolved by the resolver!&quot; (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/741";>#741</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/740";>#740</a>)</li>
   <li>b25c768 Bugfix: A root-level <code>$ref</code> to a definition that 
refers back to itself (directly or through 
<code>items</code>/<code>properties</code>) compiles instead of crashing with 
the same error (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/741";>#741</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/132";>#132</a>,
 <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/730";>#730</a>).
 The referenced definition is still emitted as its own interface alongside the 
root type</li>
   <li>107dd42 Bugfix: Index signatures from 
<code>patternProperties</code>/<code>additionalProperties</code> are widened to 
cover sibling named properties, so the interface typechecks (TS2411). Index 
signatures that already typechecked are emitted type-equivalent to before (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/704";>#704</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/671";>#671</a>)</li>
   <li>a2234d3 Bugfix: <code>inferStringEnumKeysFromValues</code> no longer 
produces invalid enum members for non-string, empty or digit-leading values (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/694";>#694</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/657";>#657</a>)</li>
   <li>377c6a1 Bugfix: A named enum (<code>tsEnumNames</code>) in a position 
with no name no longer emits a nameless <code>enum</code> declaration; it 
degrades to a union of literals (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/693";>#693</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/691";>#691</a>)</li>
   <li>c44faed Bugfix: Generated type names can no longer start with a digit or 
collapse to an empty name (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/698";>#698</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/640";>#640</a>)</li>
   <li>8d8a141 Bugfix: Recursive schemas that reach the generator without a 
name (a self-referencing <code>$ref</code> with a sibling keyword such as 
<code>description</code>, a recursive <code>oneOf</code> under 
<code>components/schemas</code>, an untitled recursive schema in another file) 
are given a generated type name instead of overflowing the stack. Schemas that 
compiled before are unchanged, except that an anonymous recursive union with a 
<code>{}</code>/<code>true</code> member now keeps its alias (same type, one 
extra <code>export type</code>) (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/760";>#760</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/482";>#482</a>,
 <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/614";>#614</a>)</li>
   </ul>
   <p>Other:</p>
   <ul>
   <li>bf06bbb Bugfix (CLI): Piping a schema on stdin no longer prints a 
<code>DEP0187</code> deprecation warning on Node 24 (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/750";>#750</a>)</li>
   <li>3abde40 Perf: <code>compile()</code> no longer scans every definition 
once per parsed node; schemas with thousands of definitions compile much faster 
(schemastore's CloudFormation schema: ~54 s -&gt; ~3 s). Generated output is 
unchanged (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/759";>#759</a>)</li>
   <li>b88891c Perf: Formatting large, mostly quote-free outputs is several 
times faster (prettier is told the output is a <code>.d.ts</code>, so it skips 
its JSX-detection scan); a caller's own <code>style.filepath</code> still wins. 
Generated output is unchanged (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/758";>#758</a>)</li>
   <li>16c2e77 Bugfix (CLI): relative <code>$ref</code>s are resolved against 
each schema file's own directory rather than <code>process.cwd()</code>, so a 
schema passed by path from another directory finds its siblings; an explicit 
<code>--cwd</code> still wins (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/742";>#742</a>,
 fixes <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/324";>#324</a>,
 <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/680";>#680</a>)</li>
   <li>9219636 Updated runtime dependencies: js-yaml 4 -&gt; 5 (YAML files 
parse as before, <a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/689";>#689</a>),
 prettier ^3.9 (short unions that fit on one line are no longer wrapped; users 
on the existing <code>^3.2.5</code> range may already see this), 
<code>@​apidevtools/json-schema-ref-parser</code> ^11.9 (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/686";>#686</a>)</li>
   <li>a5834aa Removed the <code>is-glob</code> dependency (<a 
href="https://redirect.github.com/bcherny/json-schema-to-typescript/issues/643";>#643</a>)</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li>See full diff in <a 
href="https://github.com/bcherny/json-schema-to-typescript/commits";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=json-schema-to-typescript&package-manager=npm_and_yarn&previous-version=15.0.4&new-version=16.0.0)](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]

Reply via email to