valentineus/popov.link
1
Fork 0
Code Issues Pull Requests 1 Actions Activity

fix(deps): update dependency schema-dts to v2 #27

Merged
Valentin Popov merged 1 commits from renovate/schema-dts-2.x into master 2026-04-02 16:57:06 +04:00
Conversation 0 Commits 1 Files Changed 2 +21 -6
renovate[bot] commented 2026-03-24 04:02:10 +04:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
schema-dts (source) ^1.1.5 → ^2.0.0 age confidence

Release Notes

google/schema-dts (schema-dts)

v2.0.0: schema-dts & schema-dts-gen v2.0.0

Compare Source

Changes in schema-dts

  • Supports the latest Schema.org release from Schema.org v30 -- See https://schema.org/docs/releases.html#v30.0

  • Input and Output constraints are now supported, for example:

    import type {SearchAction, WebSite, WithActionConstraints} from 'schema-dts';

const potentialAction: WithActionConstraints<SearchAction> = {
  '@&#8203;type': 'SearchAction',
  'query-input': 'required name=search_term_string',
  // ...
};

const website: WebSite = {
  '@&#8203;type': 'WebSite',
  potentialAction: {
    '@&#8203;type': 'SearchAction',
    'query-input': 'required name=search_term_string',
  } as WithActionConstraints<SearchAction>,
};

  • Breaking change: Update typings for Roles so that they are not recursive, see #​205 for more details

  • Breaking change: Quantity is now a core DataType, this is a change done in schema.org v30.0 and will technically make certain formerly-legal (but likely invalid) assignments no longer work

  • "Leaf" types are now exported. While objects like Thing or Organization require a type union that includes the object itself, it can also include any of its children. Now, if you want type something as a Thing exactly, you can import ThingLeaf which can only be a Thing and does not allow sub-types.

  • Support MergeLeafTypes, which fixes a long-running user request (#​179 #​189 #​203), allowing a multi-typed schema object to be declared. Shout out to @​mjy9088 and @​cochinescu for the work to get this working. This allows declarations like this to be made:

    import type { MergeLeafTypes,ProductLeaf, SoftwareApplicationLeaf,  WithContext } from 'schema-dts';

const app: WithContext<MergeLeafTypes<[ProductLeaf, SoftwareApplicationLeaf]>> =
  {
    '@&#8203;context': 'https://schema.org',
    '@&#8203;type': ['Product', 'SoftwareApplication'],
    name: 'My App',
    offers: {
      '@&#8203;type': 'Offer',
      price: 89,
      priceCurrency: 'USD',
    },
    operatingSystem: 'Any',
  };

    while #​189 and #​179 are not completely addressed since a random Thing cannot be a merged type, this allows some multi-type objects to exist, though they need to be explicitly declared as such by the developer.

  • Technically a breaking change: Some non-schema.org types exported in schema-dts are now renamed. These are included mostly for equivalence because the Schema.org ontology defines them, but most users should not depend on them. The names for these classes are now escaped fully-qualified IRIs instead of just the "in-context" name. This is needed because new types with the same "in-context" name have been added as external references, e.g. www.omg.org/spec/Commons/DatesAndTimes/Date which conflicts with schema.org/Date. Now, this is exported as www_omg_org_spec_Commons_DatesAndTimes_Date.

Changes in schema-dts-gen

  • Compatibility with Schema.org v30
  • Breaking change: schema.org/Quantity is now emitted as a DataType
  • Breaking change: out-of-context classes are now exported with an escaped fully-qualified IRI instead of just the hypothetical 'in-context' name. For example: www.omg.org/spec/Commons/DatesAndTimes/Date renders as Date if "@&#8203;context": "www.omg.org/spec/Commons/DatesAndTimes/" only. Otherwise, it renders as namespace_Date if "@&#8203;context" { "namespace": "www.omg.org/spec/Commons/DatesAndTimes/" }, and www_omg_org_spec_Commons_DatesAndTimes_Date if no context entry exists
  • Breaking change: the emitted output now depends on https://www.npmjs.com/package/schema-dts-lib -- the first two lines from the emitted output will include import type {...} from 'schema-dts-lib'; followed by export type { ... };.

What's Changed

New Contributors

Full Changelog: https://github.com/google/schema-dts/compare/v1.1.5...v2.0.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 this update again.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [schema-dts](https://opensource.google/projects/schema-dts) ([source](https://github.com/google/schema-dts/tree/HEAD/packages/schema-dts)) | [`^1.1.5` → `^2.0.0`](https://renovatebot.com/diffs/npm/schema-dts/1.1.5/2.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/schema-dts/2.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/schema-dts/1.1.5/2.0.0?slim=true) | --- ### Release Notes <details> <summary>google/schema-dts (schema-dts)</summary> ### [`v2.0.0`](https://github.com/google/schema-dts/releases/tag/v2.0.0): schema-dts &amp; schema-dts-gen v2.0.0 [Compare Source](https://github.com/google/schema-dts/compare/v1.1.5...v2.0.0) ### Changes in schema-dts - Supports the latest Schema.org release from Schema.org v30 -- See <https://schema.org/docs/releases.html#v30.0> - [Input and Output constraints](https://schema.org/docs/actions.html#part-4) are now supported, for example: ```ts import type {SearchAction, WebSite, WithActionConstraints} from 'schema-dts'; const potentialAction: WithActionConstraints<SearchAction> = { '@&#8203;type': 'SearchAction', 'query-input': 'required name=search_term_string', // ... }; const website: WebSite = { '@&#8203;type': 'WebSite', potentialAction: { '@&#8203;type': 'SearchAction', 'query-input': 'required name=search_term_string', } as WithActionConstraints<SearchAction>, }; ``` - **Breaking change**: Update typings for Roles so that they are not recursive, see [#&#8203;205](https://github.com/google/schema-dts/issues/205) for more details - **Breaking change**: Quantity is now a core DataType, this is a change done in schema.org v30.0 and will technically make certain formerly-legal (but likely invalid) assignments no longer work - "Leaf" types are now exported. While objects like `Thing` or `Organization` require a type union that includes the object itself, it can also include any of its children. Now, if you want type something as a `Thing` *exactly*, you can import `ThingLeaf` which can only be a Thing and does not allow sub-types. - Support `MergeLeafTypes`, which fixes a long-running user request ([#&#8203;179](https://github.com/google/schema-dts/issues/179) [#&#8203;189](https://github.com/google/schema-dts/issues/189) [#&#8203;203](https://github.com/google/schema-dts/issues/203)), allowing a multi-typed schema object to be declared. Shout out to [@&#8203;mjy9088](https://github.com/mjy9088) and [@&#8203;cochinescu](https://github.com/cochinescu) for the work to get this working. This allows declarations like this to be made: ```ts import type { MergeLeafTypes,ProductLeaf, SoftwareApplicationLeaf, WithContext } from 'schema-dts'; const app: WithContext<MergeLeafTypes<[ProductLeaf, SoftwareApplicationLeaf]>> = { '@&#8203;context': 'https://schema.org', '@&#8203;type': ['Product', 'SoftwareApplication'], name: 'My App', offers: { '@&#8203;type': 'Offer', price: 89, priceCurrency: 'USD', }, operatingSystem: 'Any', }; ``` while [#&#8203;189](https://github.com/google/schema-dts/issues/189) and [#&#8203;179](https://github.com/google/schema-dts/issues/179) are not completely addressed since a random `Thing` cannot be a merged type, this allows some multi-type objects to exist, though they need to be explicitly declared as such by the developer. - **Technically a breaking change**: Some non-schema.org types exported in schema-dts are now renamed. These are included mostly for equivalence because the Schema.org ontology defines them, but most users should not depend on them. The names for these classes are now escaped fully-qualified IRIs instead of just the "in-context" name. This is needed because new types with the same "in-context" name have been added as external references, e.g. `www.omg.org/spec/Commons/DatesAndTimes/Date` which conflicts with `schema.org/Date`. Now, this is exported as `www_omg_org_spec_Commons_DatesAndTimes_Date`. ### Changes in schema-dts-gen - Compatibility with Schema.org v30 - **Breaking change:** schema.org/Quantity is now emitted as a DataType - **Breaking change:** out-of-context classes are now exported with an escaped fully-qualified IRI instead of just the hypothetical 'in-context' name. For example: `www.omg.org/spec/Commons/DatesAndTimes/Date` renders as `Date` if `"@&#8203;context": "www.omg.org/spec/Commons/DatesAndTimes/"` only. Otherwise, it renders as `namespace_Date` if `"@&#8203;context" { "namespace": "www.omg.org/spec/Commons/DatesAndTimes/" }`, and `www_omg_org_spec_Commons_DatesAndTimes_Date` if no context entry exists - **Breaking change:** the emitted output now depends on `https://www.npmjs.com/package/schema-dts-lib` -- the first two lines from the emitted output will include `import type {...} from 'schema-dts-lib';` followed by `export type { ... };`. #### What's Changed - Support Input and Output constraints by [@&#8203;Eptagone](https://github.com/Eptagone) in [#&#8203;202](https://github.com/google/schema-dts/pull/202) - prevent `Role` from forming malformed intersections by [@&#8203;HunterLarco](https://github.com/HunterLarco) in [#&#8203;205](https://github.com/google/schema-dts/pull/205) - Make schema-dts-gen compatible with Schema.org v30 by [@&#8203;Eyas](https://github.com/Eyas) in [#&#8203;211](https://github.com/google/schema-dts/pull/211) - Docs: add real-world usage examples for common schema types by [@&#8203;cochinescu](https://github.com/cochinescu) in [#&#8203;209](https://github.com/google/schema-dts/pull/209) - Factor out common types that don't depend on the exact schema into schema-dts-lib by [@&#8203;Eyas](https://github.com/Eyas) in [#&#8203;213](https://github.com/google/schema-dts/pull/213) - Add `MergeLeafTypes` helper and export leaf types by [@&#8203;cochinescu](https://github.com/cochinescu) in [#&#8203;210](https://github.com/google/schema-dts/pull/210) #### New Contributors - [@&#8203;Eptagone](https://github.com/Eptagone) made their first contribution in [#&#8203;202](https://github.com/google/schema-dts/pull/202) - [@&#8203;Fabious](https://github.com/Fabious) made their first contribution in [#&#8203;204](https://github.com/google/schema-dts/pull/204) - [@&#8203;HunterLarco](https://github.com/HunterLarco) made their first contribution in [#&#8203;205](https://github.com/google/schema-dts/pull/205) - [@&#8203;thernstig](https://github.com/thernstig) made their first contribution in [#&#8203;206](https://github.com/google/schema-dts/pull/206) - [@&#8203;cochinescu](https://github.com/cochinescu) made their first contribution in [#&#8203;209](https://github.com/google/schema-dts/pull/209) - [@&#8203;mjy9088](https://github.com/mjy9088) opened [#&#8203;203](https://github.com/google/schema-dts/issues/203) with code that helped inform [#&#8203;210](https://github.com/google/schema-dts/issues/210) **Full Changelog**: <https://github.com/google/schema-dts/compare/v1.1.5...v2.0.0> </details> --- ### 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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNS43IiwidXBkYXRlZEluVmVyIjoiNDMuMjUuNyIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJhdXRvbWF0ZWQiLCJkZXBlbmRlbmNpZXMiXX0=-->
renovate[bot] added 1 commit 2026-03-24 04:02:10 +04:00
fix(deps): update dependency schema-dts to v2
All checks were successful
Test / npm test (push) Successful in 53s
Details
Test / npm test (pull_request) Successful in 46s
Details
3597f9e1fd
Valentin Popov was assigned by renovate[bot] 2026-03-24 04:02:10 +04:00
Valentin Popov merged commit 8a22d82d20 into master 2026-04-02 16:57:06 +04:00
Valentin Popov deleted branch renovate/schema-dts-2.x 2026-04-02 16:57:06 +04:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovatebot renovate[bot] valentineus Valentin Popov
No Assignees Valentin Popov
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: valentineus/popov.link#27
Delete Branch "renovate/schema-dts-2.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?