build(deps): bump @utrecht/paragraph-css from 2.3.1 to 3.0.1

[dependabot]

Bumps @utrecht/paragraph-css from 2.3.1 to 3.0.1.

Release notes

Sourced from @​utrecht/paragraph-css's releases.

@​utrecht/button-react@​3.0.1

Patch Changes

• Updated dependencies [7c6f825]
  • @​utrecht/button-css@​3.1.0

@​utrecht/component-library-vue@​3.0.1

Patch Changes

• e80b151: Resolve type errors on dependencies update for Image component by aligning <img> width and height attribute typings with Vue’s Numberish type (string | number) instead of CSSNumberish.

@​utrecht/web-component-library-vue@​3.0.1

Patch Changes

• Updated dependencies [0873069]
  • @​utrecht/web-component-library-stencil@​4.1.0

@​utrecht/button-react@​3.0.0

Major Changes

• 0873069: Updated typescript props to give an error when using non valid strings for the Hint and Appearance property.

  Property guards properly narrowed to property options.

@​utrecht/web-component-library-angular@​3.0.1

Patch Changes

• a98c3cc: Upgrade tslib dependency to 2.6.3

@​utrecht/component-library-angular@​3.0.1

Patch Changes

• a98c3cc: Upgrade tslib dependency to 2.6.3

@​utrecht/component-library-vue@​3.0.0

Major Changes

• edac79f: - badge-status is no longer styled through common badge tokens but has its own set of tokens
  • badge-status has been renamed to status-badge, use @​utrecht/status-badge-css instead of @​utrecht/badge-status-css

@​utrecht/web-component-library-angular@​3.0.0

Major Changes

• edac79f: - badge-status is no longer styled through common badge tokens but has its own set of tokens
  • badge-status has been renamed to status-badge, use @​utrecht/status-badge-css instead of @​utrecht/badge-status-css

@​utrecht/component-library-angular@​3.0.0

Major Changes

• edac79f: - badge-status is no longer styled through common badge tokens but has its own set of tokens

... (truncated)

Changelog

Sourced from @​utrecht/paragraph-css's changelog.

3.0.1

Patch Changes

• 9b3cb1e: Release with npm provenance.

3.0.0

Major Changes

• 77438bb: # BREAKING CHANGE: Migrate from SCSS @​import to @use/@​forward

  Migrated all SCSS files from the legacy @import syntax to the modern @use and @forward module system.

  Breaking Changes

  • Import syntax changed: @import statements replaced with @use/@forward
  • Namespace requirements: Some imports now require explicit namespaces
  • File structure: Added _forward.scss files for mixin exports
  • Module loading: Modules are now loaded once and cached

  Migration Guide

  For CSS Classes

  // Before
  @import "~@utrecht/button-css/src/index";
  // After (recommended)
  @​use "~@utrecht/button-css/src/index";
  // Note: @​import still works for CSS-only files but @​use is recommended

  For Mixins

  // Before
  @import "~@utrecht/button-css/src/mixin";
  @include utrecht-button;
  // After
  @​use "~@utrecht/button-css/src/forward" as *;
  @​include utrecht-button;

  With Namespaces

... (truncated)

Commits

• e8d701f docs(release): design system packages
• 5144cbf docs(release): design system packages
• 77438bb feat: migrate from SCSS @​import to @use/@​forward
• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​utrecht/paragraph-css since your current version.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
rijkshuisstijl-community	Ignored	Preview	Apr 15, 2026 8:27am
rijkshuisstijl-community-storybook-angular	Ignored	Preview	Apr 15, 2026 8:27am
rijkshuisstijl-community-templates	Ignored	Preview	Apr 15, 2026 8:27am

[changeset-bot]

⚠️ No Changeset found

Latest commit: a8999ad

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud