Skip to content

Fix insiders tags sometimes published to latest channel#453

Merged
RobinMalfait merged 1 commit intotailwindlabs:mainfrom
wongjn:hotfix/release-channel
Apr 24, 2026
Merged

Fix insiders tags sometimes published to latest channel#453
RobinMalfait merged 1 commit intotailwindlabs:mainfrom
wongjn:hotfix/release-channel

Conversation

@wongjn
Copy link
Copy Markdown
Contributor

@wongjn wongjn commented Apr 23, 2026

Credit to @0xsvenka for discovering this.

As per my findings:

It seems like the releases tagged 0.0.0-insiders.* are incorrectly assigned the latest channel when published to NPM. I believe this is because the regex to determine the channel does not resolve to be insiders. I.e. for 0.0.0-insiders.f7d2598, we can see in the GitHub workflow run it is published to the latest channel. Compare this to 0.0.0-insiders.3b0ed57 which publishes correctly to insiders. This is because 0.0.0-insiders.3b0ed57 does match the regex.

This PR relaxes the regex to not need a digit after the dot (.), allowing matches for tags like 0.0.0-insiders.ffaa88.

Copy link
Copy Markdown
Member

@RobinMalfait RobinMalfait left a comment

Choose a reason for hiding this comment

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

Good catch! I already fixed up tag on npm itself, but this is indeed a bug. Thanks!

@RobinMalfait RobinMalfait merged commit 0a7ddcb into tailwindlabs:main Apr 24, 2026
1 check passed
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.

2 participants