browser-specs - npm Package Compare versions

Comparing version 1.43.0 to 1.44.0

CHANGELOG.md

		@@ -7,2 +7,20 @@ # Changelog

		## [1.44.0](https://github.com/w3c/browser-specs/compare/1.43.0...1.44.0) - 2021-07-02

		### Merged

		- Add fingerprinting-guidance to the list of specs. [`#326`](https://github.com/w3c/browser-specs/pull/326)
		- Bump version of github-push-action [`#329`](https://github.com/w3c/browser-specs/pull/329)
		- Add IETF specs used in MDN [`#325`](https://github.com/w3c/browser-specs/pull/325)
		- Make "main" branch the default branch [`#324`](https://github.com/w3c/browser-specs/pull/324)

		### Fixed

		- Add IETF specs used in MDN (#325) [`#280`](https://github.com/w3c/browser-specs/issues/280)

		### Commits

		- Fix version number in build workflow [`8975664`](https://github.com/w3c/browser-specs/commit/89756641590182df1e62e4333d03f7d048cdf118)
		- Explicit default branch name in build workflow [`56acce2`](https://github.com/w3c/browser-specs/commit/56acce2f654a85d43d8368e9784fc63dc17acf7a)

		## [1.43.0](https://github.com/w3c/browser-specs/compare/1.42.0...1.43.0) - 2021-07-01
		@@ -9,0 +27,0 @@

package.json

README.md

		@@ -465,3 +465,3 @@ # Web browser specifications
		4. The spec sits at the application layer or is "close to it". For instance,
		IETF specs are essentially out of scope, at least for now.
		most IETF specs are likely out of scope, but some that are exposed to Web developers are in scope.
		5. The spec defines normative content (terms, CSS, IDL), or it contains
		@@ -554,3 +554,3 @@ informative content that other specs often need to refer to (e.g. guidelines
		new version through the following command, to be run from an up-to-date local
		`master` branch:
		`main` branch:

		@@ -557,0 +557,0 @@ ```bash

index.json

Sorry, the diff of this file is too big to display

New alerts