Skip to content

Update dependency @frontify/fondue to v13#37

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/frontify-fondue-13.x
Open

Update dependency @frontify/fondue to v13#37
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/frontify-fondue-13.x

Conversation

@renovate

@renovate renovate Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@frontify/fondue (source) 12.0.0-beta.2013.7.4 age confidence

Release Notes

Frontify/fondue (@​frontify/fondue)

v13.7.4

Compare Source

Patch Changes

v13.7.3

Compare Source

Patch Changes
  • #​2797 19809e5 Thanks @​SamuelAlev! - Pin the Badge text to the regular font weight so it no longer inherits a bold weight from an ancestor with font-weight: bold.

  • #​2802 24f103b Thanks @​noahwaldner! - feat: split up the guides into smaller files

  • #​2799 033ffae Thanks @​noahwaldner! - feat: remove custom skill install script

  • #​2801 a086574 Thanks @​noahwaldner! - Harden the Fondue SDK contract ahead of the 1.0 release (still prerelease, 0.x):

    • Component status is now always set. The manifest parser understands const meta = { … } satisfies Meta<…> story files, the six components whose stories weren't wired up (LoadingBar, LoadingCircle, RouterProvider, Section, Text, ThemeProvider) now expose their Storybook status, and icons are bundled as 'released'.
    • Data-derived literal unions. status, category, and token category are typed as ComponentStatus, ComponentCategory, and TokenCategory (exported), so a typo in a filter fails at compile time instead of silently matching nothing.
    • New components.statuses() / components.status(name) facet accessors, mirroring categories and tags.
    • Uniform identity. Every entity now carries a canonical id; for components it equals name. The redundant ComponentDetails.subComponentNames was dropped (use subComponents[].name).
    • null for not-applicable fields. ComponentNode.instructions and ComponentProp.deprecationMessage are string | null instead of sometimes-empty strings; Token.cssVariable is string | null for inlined-literal tokens.
    • Segment-aware keyPathStartsWith. The prefix 'colors.chart' no longer matches colors.charts.*; filter edge cases (empty-array clauses, empty text) are now documented behavior.
    • Deep-frozen data. Nodes, toJSON() payloads, and the arrays returned by list() are frozen — mutating shared SDK state now throws instead of silently corrupting other consumers.
    • Build-time data validation. The SDK build fails on missing statuses/categories, dangling relatedComponents references, duplicate ids, and token/cssVariable inconsistencies.
    • Packaging: sideEffects: false, engines bumped to Node 20+, and the *-prefix tailwindClass placeholder convention is documented.
  • #​2800 a5ceef1 Thanks @​noahwaldner! - feat: add deprecation notices to legacy components

  • Updated dependencies [19809e5, 24f103b, 033ffae, a086574, a5ceef1]:

v13.7.2

Compare Source

Patch Changes

v13.7.1

Compare Source

Patch Changes

v13.7.0

Compare Source

Minor Changes
Patch Changes

v13.6.5

Compare Source

Patch Changes

v13.6.4

Compare Source

Patch Changes

v13.6.2

Compare Source

Patch Changes

v13.6.1

Compare Source

Patch Changes

v13.6.0

Compare Source

Minor Changes
Patch Changes

v13.5.1

Compare Source

Patch Changes

v13.5.0

Compare Source

Minor Changes
Patch Changes

v13.4.5

Compare Source

Patch Changes

v13.4.4

Compare Source

Patch Changes

v13.4.3

Compare Source

Patch Changes

v13.4.2

Compare Source

Patch Changes

v13.4.1

Compare Source

Patch Changes

v13.4.0

Compare Source

Minor Changes
Patch Changes

v13.3.2

Compare Source

Patch Changes

v13.3.1

Compare Source

Patch Changes

v13.3.0

Compare Source

Minor Changes
Patch Changes

v13.2.0

Compare Source

Minor Changes
Patch Changes

v13.1.5

Compare Source

Patch Changes

v13.1.4

Compare Source

Patch Changes

v13.1.3

Compare Source

Patch Changes

v13.1.2

Compare Source

Patch Changes

v13.1.1

Compare Source

Patch Changes

v13.0.0

Major Changes
Minor Changes
Patch Changes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Zurich)

  • Branch creation
    • "after 9pm,before 6am"
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: glyphs_preview_block@1.0.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18" from @frontify/fondue@13.7.4
npm ERR! node_modules/@frontify/fondue
npm ERR!   @frontify/fondue@"13.7.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-24T22_57_38_526Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from 52979fa to 0e6854d Compare February 13, 2026 19:00
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from c15db4a to 572c8d2 Compare March 3, 2026 11:08
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch from 572c8d2 to 48e7665 Compare March 9, 2026 15:49
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from 6dd3d74 to c0705f1 Compare March 18, 2026 10:12
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from b573cc4 to c08fc4c Compare March 30, 2026 10:49
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from 8451819 to 5ed0f8f Compare April 16, 2026 13:52
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from a278c4a to 287b9ff Compare April 28, 2026 20:43
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch from 287b9ff to 0c723cb Compare May 1, 2026 15:32
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch from 0c723cb to 00e04fb Compare May 19, 2026 12:10
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 3 times, most recently from dae0603 to 7753e53 Compare May 29, 2026 12:49
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch from 7753e53 to 1ed9da9 Compare June 10, 2026 16:57
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from 1664982 to 1ae3f7b Compare June 22, 2026 16:33
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from f470926 to e6b45eb Compare July 9, 2026 12:02
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch 2 times, most recently from aebf613 to 16e7bc8 Compare July 20, 2026 23:43
@renovate
renovate Bot force-pushed the renovate/frontify-fondue-13.x branch from 16e7bc8 to 1fa006a Compare July 23, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants