Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 28, 2025

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

@sl-design-system/bingel-dc@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/bingel-int@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/clickedu@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/editorial-suite@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/itslearning@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/kampus@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/magister@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

@sl-design-system/max@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/my-digital-book@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/neon@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/sanoma-learning@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/teas@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/tig@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/panel@0.3.0

Minor Changes

  • #2842 be3b2b8 - From now on, use default and relaxed for the density property.
    The plain and comfortable values are deprecated, they will be kept for the backward compatibility for now but removed in the future.
    Please use default or relaxed from now on.

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1
    • @sl-design-system/tool-bar@0.1.2

@sl-design-system/select@2.1.0

Minor Changes

  • #2819 39b286c - Make the select adjust size automatically to the largest option

    This change updates the select component to automatically adjust its width based on the largest option available. If any of the options contain HTML elements, the automatic sizing is disabled to ensure accurate rendering. This enhancement improves the user experience by preventing text truncation and ensuring that all options are fully visible.

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/angular@3.4.1

Patch Changes

@sl-design-system/badge@1.1.4

Patch Changes

  • #2734 f676dd5 - Added the option to add a label to sm badges; this will be shown behind the dot.

@sl-design-system/button@1.3.2

Patch Changes

  • #2809 ef77be3 - Replace slotchange with MutationObserver so text changes are also detected.

    This fixes a bug in Angular where the text content of the button is changed after the custom element has been initialized, but the slotchange event does not fire. Due to slotchange not firing, the icon-only attribute isn't removed and the button styling breaks. Using a MutationObserver allows us to detect changes to the text content within the slot and fix the bug.

@sl-design-system/callout@0.0.2

Patch Changes

  • #2842 be3b2b8 - New callout component, visually similar to the inline-message but with a different purpose:
    it can be used to provide additional, non-interrupting information and may include actions (e.g. buttons).
    It must not be shown/hidden dynamically in response to user actions (unlike the inline-message).
    There is no ARIA role on this component as it is not meant to interrupt the user (no live region).
  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/data-source@0.2.3

Patch Changes

  • #2815 df7af95 - Fix data not being invalidated when calling FetchListDataSource.update()

    This fixes a bug where after adding a filter and calling update(), the fetchPage callback was not being called again. Instead the data source was still serving the old data from the previous fetchPage calls.

@sl-design-system/emoji@0.0.9

Patch Changes

  • #2734 f676dd5 - Refactored tokens for headings, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, d807cb2, ef77be3]:

    • @sl-design-system/icon@1.4.1
    • @sl-design-system/button@1.3.2

@sl-design-system/grid@0.6.4

Patch Changes

  • #2813 8ef0b55 - Improve reliability of selection mode

    When you add an <sl-grid-selection-column> to a grid, the selection column automatically enables multiple selection mode on the data source. However, if you then changed the items property, the new data source would not have selection enabled. This fixes both cases by having a selects property on grid that is kept in sync with the data source. The selection column also sets the selects property on the grid.

  • Updated dependencies [df7af95, f676dd5, 39b286c, f676dd5, 891f599, d807cb2, ef77be3]:

    • @sl-design-system/data-source@0.2.3
    • @sl-design-system/icon@1.4.1
    • @sl-design-system/select@2.1.0
    • @sl-design-system/toggle-group@0.0.11
    • @sl-design-system/search-field@0.2.2
    • @sl-design-system/button@1.3.2
    • @sl-design-system/tool-bar@0.1.2

@sl-design-system/icon@1.4.1

Patch Changes

  • #2734 f676dd5 - Refactored token for multi-colour icons, this was still using tokens that have now moved to the deprecated css files.

  • #2812 d807cb2 - Change IconPrefix type so we no longer get errors every time a new prefix is added in FontAwesome

@sl-design-system/menu@0.2.7

Patch Changes

  • #2734 f676dd5 - Refactored tokens for icon sizes and focus outline, these were still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, d807cb2, ef77be3]:

    • @sl-design-system/icon@1.4.1
    • @sl-design-system/button@1.3.2

@sl-design-system/paginator@0.2.2

Patch Changes

  • #2734 f676dd5 - Refactored tokens for padding, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, 39b286c, d807cb2, f676dd5, ef77be3]:

    • @sl-design-system/icon@1.4.1
    • @sl-design-system/select@2.1.0
    • @sl-design-system/menu@0.2.7
    • @sl-design-system/button@1.3.2

@sl-design-system/progress-bar@0.1.4

Patch Changes

  • #2734 f676dd5 - Refactored tokens for border-radius, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, d807cb2]:

    • @sl-design-system/icon@1.4.1

@sl-design-system/search-field@0.2.2

Patch Changes

  • #2816 891f599 - Debounce the sl-search event while typing

    Previously applications using the search field component would have to debounce the sl-search event themselves. With this change the component now debounces the event internally with a default delay of 300ms.

@sl-design-system/tabs@1.2.4

Patch Changes

  • #2828 538bedd - Align the styling with Figma of the tab indicator (increased width and border radius) and the part="container" (increased border width).

  • Updated dependencies [f676dd5, d807cb2, f676dd5]:

    • @sl-design-system/icon@1.4.1
    • @sl-design-system/menu@0.2.7

@sl-design-system/tag@0.1.8

Patch Changes

  • #2734 f676dd5 - Refactored token for icon sizing, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, d807cb2]:

    • @sl-design-system/icon@1.4.1

@sl-design-system/time-field@0.0.2

Patch Changes

  • #2824 ff5b844 - Multiple fixes:

    • For required time-field, native validation message is now used. The custom message "Please enter a time." appears only when the entered value is not a valid time.
    • Fixed an issue where the dialog time picker value did not update when the user typed a new value.
  • #2802 c8eab5b - Fixes toggling time picker when clicking on the clock button.

  • Updated dependencies [f676dd5, d807cb2]:

    • @sl-design-system/icon@1.4.1

@sl-design-system/toggle-button@0.0.11

Patch Changes

  • #2734 f676dd5 - Refactored token for icon sizing, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5, d807cb2]:

    • @sl-design-system/icon@1.4.1

@sl-design-system/toggle-group@0.0.11

Patch Changes

  • #2734 f676dd5 - Refactored token for focus ring, this was still using tokens that have now moved to the deprecated css files.

  • Updated dependencies [f676dd5]:

    • @sl-design-system/toggle-button@0.0.11

@sl-design-system/tool-bar@0.1.2

Patch Changes

  • Updated dependencies [f676dd5, f676dd5, f676dd5, d807cb2, f676dd5, ef77be3]:
    • @sl-design-system/toggle-button@0.0.11
    • @sl-design-system/icon@1.4.1
    • @sl-design-system/toggle-group@0.0.11
    • @sl-design-system/menu@0.2.7
    • @sl-design-system/button@1.3.2

@sl-design-system/tree@0.2.1

Patch Changes

  • #2811 1d21347 - Fix lazy loaded children to inherit the selected state of the parent node

  • Updated dependencies [df7af95, f676dd5, d807cb2]:

    • @sl-design-system/data-source@0.2.3
    • @sl-design-system/icon@1.4.1

@sl-design-system/myvanin@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@sl-design-system/sanoma-utbildning@1.0.0

Major Changes

  • #2734 f676dd5 - This is a major change after the refactoring of the Figma tokens and subsequently the webcomponents; with this release we removed the old tokens from the default css files, and moved all legacy tokens to a separate file. This means a breaking change; if you have components in your application that are not updated yet to the version that uses the new tokens the styling will be broken if you don't take action after using this version of the theme.
    To support these older component versions you can include light-deprecated.css in all places where you now include light.css until all components are updated and you can remove the legacy file.
    (light.css is taken as an example, this of course goes for all files, also dark, base and the scss files)

Patch Changes

  • Updated dependencies [f676dd5, d807cb2]:
    • @sl-design-system/icon@1.4.1

@github-actions github-actions bot force-pushed the changeset-release/main branch from 93fbe4b to 5acdb08 Compare October 28, 2025 16:03
@github-actions github-actions bot force-pushed the changeset-release/main branch 2 times, most recently from 785d326 to a5fe7f1 Compare November 5, 2025 12:10
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 1009a94 to af77055 Compare November 18, 2025 15:20
@github-actions github-actions bot force-pushed the changeset-release/main branch from af77055 to 6f2f145 Compare November 21, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant