Skip to content

Conversation

@Barsnes
Copy link
Member

@Barsnes Barsnes commented Jan 12, 2026

Summary

Due to a wrong configuration with our snapshot release we accidentally released version 1.10.0.
This version will be removed from NPM, but it will still block us from publishing a new release with this version number.
We will have to manually bump to 1.10.0 so that our release PR will bump to 1.11.0

I am including a changeset about this so consumers understand why 1.10.0 is skipped in the changelog and in released on NPM

See: https://docs.npmjs.com/policies/unpublish#considerations

Checks

@changeset-bot
Copy link

changeset-bot bot commented Jan 12, 2026

🦋 Changeset detected

Latest commit: c241792

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@digdir/designsystemet Minor
@digdir/designsystemet-css Minor
@digdir/designsystemet-react Minor
@digdir/designsystemet-theme Minor
@digdir/designsystemet-types Minor

Not sure what this means? Click here to learn what changesets are.

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

@Barsnes
Copy link
Member Author

Barsnes commented Jan 12, 2026

We can merge this after NPM has removed the wrongly released versions

@github-actions
Copy link
Contributor

github-actions bot commented Jan 12, 2026

Preview deployments for this pull request:

storybook - 14. Jan 2026 - 11:45

@Barsnes Barsnes marked this pull request as ready for review January 13, 2026 07:12
@mimarz
Copy link
Collaborator

mimarz commented Jan 13, 2026

I dont think we need this anymore, as it will be bundled together with the other changesets in the pipeline, making this information just confusing.

@Barsnes
Copy link
Member Author

Barsnes commented Jan 13, 2026

I dont think we need this anymore, as it will be bundled together with the other changesets in the pipeline, making this information just confusing.

I strongly disagree.
Every changelog will have a jump from 1.9.0 to 1.11.0.
It is important that we inform our users, both on npm and in the changelog that version 1.10.0 should not be used,

mimarz
mimarz previously requested changes Jan 13, 2026
@mimarz
Copy link
Collaborator

mimarz commented Jan 13, 2026

I dont think we need this anymore, as it will be bundled together with the other changesets in the pipeline, making this information just confusing.

I strongly disagree. Every changelog will have a jump from 1.9.0 to 1.11.0. It is important that we inform our users, both on npm and in the changelog that version 1.10.0 should not be used,

Ok, doesn't hurt to inform everywhere we can :)

Copy link
Collaborator

@oddvernes oddvernes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤞

@mimarz mimarz self-requested a review January 14, 2026 10:51
@mimarz mimarz merged commit 4d48a81 into main Jan 14, 2026
17 checks passed
@mimarz mimarz deleted the release/fix-numbers branch January 14, 2026 10:51
@github-actions github-actions bot mentioned this pull request Jan 14, 2026
Barsnes added a commit that referenced this pull request Jan 20, 2026
Co-authored-by: Michael Marszalek <mimarz@gmail.com>
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.

4 participants