ci: check for API changes in @digdir/designsystemet

[unekinn]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a522cf7

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

[github-actions]

Preview deployments for this pull request:

Storybook - 8. Nov 2024 - 12:08

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	53.9%	3067 / 5690
🔵	Statements	53.9%	3067 / 5690
🔵	Functions	85.85%	170 / 198
🔵	Branches	74.75%	459 / 614

File Coverage

No changed files found.

Generated in workflow #849 for commit a522cf7 by the Vitest Coverage Report Action

[unekinn]

@mimarz Here's an example of changing a part of the public API, and the resulting build error.

To update the api report in the repo, you would need to run yarn report:cli-api --local, get this diff

Then check it in and commit, thus making it obvious in the PR that the API has changed.

Question: I feel like the yarn report:cli-api --local command has to be documented. But where?

[unekinn]

Checked that it works in CI 👍

[mimarz]

I haven't added a README file to the CLI yet, but I feel like its natural to something like that document there? #2732