Skip to content

Commit 676c483

Browse files
Prepare release 2.1.0 (#130)
1 parent 2570079 commit 676c483

File tree

5 files changed

+20
-9
lines changed

5 files changed

+20
-9
lines changed

CHANGELOG.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,17 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
1717
<!-- ### Removed -->
1818
<!-- ### Fixed -->
1919

20-
## Unreleased
20+
## [2.1.0] - 2024-05-16
21+
22+
### Added
23+
24+
- Added `readonly` flag to `PropertyLike`, the common interface of variables, class fields, and function parameters. ([#118](https://github.com/webcomponents/custom-elements-manifest/pull/#118))
25+
26+
- Added support for describing the [CSS Custom State](https://developer.mozilla.org/en-US/docs/Web/API/CustomStateSet) of an element. ([#128](https://github.com/webcomponents/custom-elements-manifest/pull/128))
2127

2228
### Fixed
2329

24-
- Clarified that all attributes of a `CustomElement` must be listed in the the `attributes` array, even those reflected from a `CustomElementField`.
30+
- Clarified that all attributes of a `CustomElement` must be listed in the the `attributes` array, even those reflected from a `CustomElementField`. ([#126](https://github.com/webcomponents/custom-elements-manifest/pull/126))
2531

2632
## [2.0.0] - 2022-09-12
2733

README.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,14 @@ In order to allow tools to find npm packages with custom element manifests witho
3737
## Schema Versioning
3838

3939
The schema has a `schemaVersion` field in the top-level object to facilitate
40-
evolution of the schema. The schema follows [semver](https://semver.org/) versioning, the current schema version is `2.0.0`.
40+
evolution of the schema. The schema follows [semver](https://semver.org/) versioning, the current schema version is `2.1.0`.
4141

42-
This version will not always match the npm package version, as some changes to the npm package might not have changes to the schema. We will publish a list of schema versions and their associated npm versions and git tags.
42+
This version may not always match the npm package version, as some changes to the npm package might not have changes to the schema.
43+
44+
| Schema Version | Date | npm Version | git Tag |
45+
| -------------- | ---------- | ----------- | ------- |
46+
| 2.1.0 | 2024-05-06 | 2.1.0 | v2.2.0 |
47+
| 2.0.0 | 2022-09-13 | 2.0.0 | v2.0.0 |
4348

4449
## Example
4550

@@ -75,7 +80,7 @@ The manifest would look like:
7580
`my-project/custom-elements.json`:
7681
```json
7782
{
78-
"schemaVersion": "2.0.0",
83+
"schemaVersion": "2.1.0",
7984
"readme": "README.md",
8085
"modules": [
8186
{

examples/simple-element.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"schemaVersion": "2.0.0",
2+
"schemaVersion": "2.1.0",
33
"readme": "README.md",
44
"modules": [
55
{

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "custom-elements-manifest",
3-
"version": "2.0.0",
3+
"version": "2.1.0",
44
"description": "A file format for describing custom elements",
55
"type": "module",
66
"main": "schema.json",

0 commit comments

Comments
 (0)