Skip to content

Commit 47b1852

Browse files
committed
Get ready for @webref/css v7 release, drop alpha flag
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.
1 parent 8681b3c commit 47b1852

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

packages/css/CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Webref adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
77
applied to data. A new major version is released whenever a breaking change is
88
made to the data structure.
99

10-
## v7.0.x - 2025-TBD
10+
## v7.0.11 - 2025-09-04
1111

1212
CSS extracts are now consolidated into a single file.
1313

@@ -25,7 +25,7 @@ In version 6, `listAll()` resolved with an object where the keys were spec short
2525
- The consolidation removes duplicates, merging extended definitions into a single feature. The definition from the latest spec level is used when a feature is defined in more than one level. If you need the definition from earlier levels, please [raise an issue](https://github.com/w3c/webref/issues) to describe your needs!
2626
- Some of the possible values that a CSS feature could take appeared nested under that feature definition in a `values` key in version 6. Such values are no longer reported in the new version: they were confusing in any case because they did not cover the whole range of values that a feature could take, and could contain values that were not atomic keyword values. Values could be re-introduced when CSS specs are more systematic about them. In the meantime, you will need to parse the feature's syntax (the `syntax` key) to extract keyword values.
2727

28-
Additionally, the package now also exposes a new `index()` async method that resolves with an object similar to that returned by `listAll()`, except that lists of features under each category are indexed by feature names. For scoped features, the feature name is used as identifier when it is unambiguous. If a feature is defined differently for different scopes, the feature name is completed with the name of the first scoping feature to disambiguate. For example, `type() for @function`, `type() for attr()`.
28+
Additionally, the package now also exposes a new `index()` async method that resolves with an object similar to that returned by `listAll()`, except that lists of features under each category are indexed by feature names. For scoped features, the feature name is used as identifier when it is unambiguous. If a feature is defined differently for different scopes, the feature name is completed with the name of the first scoping feature to disambiguate. For example, `type() for @function`, `type() for attr()`.
2929

3030
## v6.0.0 - 2022-11-28
3131

packages/css/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "@webref/css",
33
"description": "CSS definitions of the web platform",
4-
"version": "7.0.11-alpha",
4+
"version": "7.0.11",
55
"repository": {
66
"type": "git",
77
"url": "https://github.com/w3c/webref.git"

0 commit comments

Comments
 (0)