fix(deps): update dependency typia to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typia (source)	8.1.1 -> 9.1.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

samchon/typia (typia)

v9.1.1

Compare Source

What's Changed

• Close #​1568: native type from @types/node by @​samchon in https://github.com/samchon/typia/pull/1569

Full Changelog: samchon/typia@9.1.0...v9.1.1

v9.1.0

Compare Source

What's Changed

• Bump the ecosystem group across 1 directory with 3 updates by @​dependabot in https://github.com/samchon/typia/pull/1565
• Bump typescript from 5.8.2 to 5.8.3 in /test in the ecosystem group by @​dependabot in https://github.com/samchon/typia/pull/1566
• New function typia.json.schema<T>() by @​samchon in https://github.com/samchon/typia/pull/1567

Full Changelog: samchon/typia@v9.0.1...9.1.0

v9.0.1

Compare Source

Major update from @samchon/openapi: https://github.com/samchon/openapi/releases/tag/v4.0.0

export namespace JsonSchema {
  export interface INumber {
    type: "number";
    minimum?: number;
    maximum?: number;
    exclusiveMinimum?: number; // boolean -> number
    exclusiveMaximum?: number; // boolean -> number;
    examples?: Record<string, any> | Array<any>; // object -> array | object
  }
}

Anthropic Claude has banned boolean typed exclusiveMinimum and exclusiveMaximum properties. So @samchon/openapi has changed them to number type to support Anthropic Claude perflectly, and it is a typical major update taking a break change on types.

Also, in the JSON schema specifications, examples property has been changed from Array<any> type to Record<string, any> type since OpenAPI v3 update. However, too much people and frameworks are not responding such specification change. So, many of users validating OpenAPI specification by typia.assert<OpenApiV3_1.IDocument>(doc) function had been failed due to such JsonSchema.examples reason.

@samchon/openapi's new release allows non-standard example type (Array<any>) considering the industrial environments, and supports polyfill methods instead.

To respond such break changes with major update from @samchon/openapi, typia has released new major update v9. Also, realising a new major update, typia has enhanced number & tags.Type<"uint32"> like unsigned integer type about JSON schema generation. From now on, when define a number & tags.Type<"int32"> like tag, it would also contain the minimum: 0 constraint in the JSON schema.

What's Changed

• exclusiveMinimum/exclusiveMaximum as number type by @​samchon in https://github.com/samchon/typia/pull/1562
• Enhance uint type's JSON schema property. by @​samchon in https://github.com/samchon/typia/pull/1563
• Fix comment tag written @exclusiveMinimum case. by @​samchon in https://github.com/samchon/typia/pull/1564

Full Changelog: samchon/typia@v8.2.0...v9.0.1

v9.0.0

Compare Source

v8.2.0

Compare Source

What's Changed

• Prepare example codes for nextra v4 mdx compiling by @​samchon in https://github.com/samchon/typia/pull/1558
• fix typo: validatae -> validate by @​dengkunli in https://github.com/samchon/typia/pull/1560
• Bump up openapi version by @​samchon in https://github.com/samchon/typia/pull/1561

New Contributors

• @​dengkunli made their first contribution in https://github.com/samchon/typia/pull/1560

Full Changelog: samchon/typia@v8.1.1...v8.2.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.