Get ready for @webref/css v7 release, drop alpha flag
#1660
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Time to give v7 a try in real life, following iterations and discussions in: #1519 Note: the way we managed alpha versions was somewhat clunky. The version increment should have appeared *after* the `alpha` flag. This update drops the `alpha` flag, which means that the first actual published package will be `7.0.11` and not `7.0.0`. Plan is to continue to publish v6 for a little while to give consumers enough time to adjust their code and provide a fallback plan should the new version turn out to be impractical.
dontcallmedom
approved these changes
Sep 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Time to give v7 a try in real life, following iterations and discussions in: #1519
Note: the way we managed alpha versions was somewhat clunky. The version increment should have appeared after the
alphaflag. This update drops thealphaflag, which means that the first actual published package will be7.0.11and not7.0.0.Plan is to continue to publish v6 for a little while to give consumers enough time to adjust their code and provide a fallback plan should the new version turn out to be impractical.
Another note: it's possible that an actual CSS update is needed for the code that detects the need to publish new releases to work. There should be no hurry to publish in any case...