Skip to content

Commit

Permalink
Prepare release 2.1.0 (#130)
Browse files Browse the repository at this point in the history
  • Loading branch information
justinfagnani authored May 6, 2024
1 parent 2570079 commit 676c483
Show file tree
Hide file tree
Showing 5 changed files with 20 additions and 9 deletions.
10 changes: 8 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,11 +17,17 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
<!-- ### Removed -->
<!-- ### Fixed -->

## Unreleased
## [2.1.0] - 2024-05-16

### Added

- 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))

- 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))

### Fixed

- Clarified that all attributes of a `CustomElement` must be listed in the the `attributes` array, even those reflected from a `CustomElementField`.
- 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))

## [2.0.0] - 2022-09-12

Expand Down
11 changes: 8 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,14 @@ In order to allow tools to find npm packages with custom element manifests witho
## Schema Versioning

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

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.
This version may not always match the npm package version, as some changes to the npm package might not have changes to the schema.

| Schema Version | Date | npm Version | git Tag |
| -------------- | ---------- | ----------- | ------- |
| 2.1.0 | 2024-05-06 | 2.1.0 | v2.2.0 |
| 2.0.0 | 2022-09-13 | 2.0.0 | v2.0.0 |

## Example

Expand Down Expand Up @@ -75,7 +80,7 @@ The manifest would look like:
`my-project/custom-elements.json`:
```json
{
"schemaVersion": "2.0.0",
"schemaVersion": "2.1.0",
"readme": "README.md",
"modules": [
{
Expand Down
2 changes: 1 addition & 1 deletion examples/simple-element.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"schemaVersion": "2.0.0",
"schemaVersion": "2.1.0",
"readme": "README.md",
"modules": [
{
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "custom-elements-manifest",
"version": "2.0.0",
"version": "2.1.0",
"description": "A file format for describing custom elements",
"type": "module",
"main": "schema.json",
Expand Down

0 comments on commit 676c483

Please sign in to comment.