chore: release packages

[fondue-release-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@frontify/fondue-sdk@0.2.0

Minor Changes

• #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.

Patch Changes

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

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

@frontify/fondue-components@31.0.1

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.

• #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 []:

  • @frontify/fondue-tokens@5.1.0

@frontify/fondue@13.7.3

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]:

  • @frontify/fondue-components@31.0.1
  • @frontify/fondue-sdk@0.2.0

[netlify]

✅ Deploy Preview for fondue-components ready!

Name	Link
🔨 Latest commit	ad1af16
🔍 Latest deploy log	https://app.netlify.com/projects/fondue-components/deploys/6a59e9e0b2c8630007d51217
😎 Deploy Preview	https://deploy-preview-2798.components.fondue-components.frontify.com
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.