commit-and-tag-version - npm Package Compare versions

Comparing version 11.2.0 to 11.2.1

lib/stringify-package.js

test/stringify-package.spec.js

CHANGELOG.md

		@@ -5,2 +5,9 @@ # Changelog

		## [11.2.1](https://github.com/absolute-version/commit-and-tag-version/compare/v11.2.0...v11.2.1) (2023-04-05)


		### Bug Fixes

		* dep: add stringify-package to project source, removing the deprecation warning on npm install ([#65](https://github.com/absolute-version/commit-and-tag-version/issues/65)) ([3a959a7](https://github.com/absolute-version/commit-and-tag-version/commit/3a959a7eba86ad42b98592167df7c67f00b661a0))

		## [11.2.0](https://github.com/absolute-version/commit-and-tag-version/compare/v11.1.0...v11.2.0) (2023-03-15)
		@@ -7,0 +14,0 @@

lib/updaters/types/json.js

		@@ -1,2 +0,2 @@
		const stringifyPackage = require('stringify-package')
		const stringifyPackage = require('../../stringify-package')
		const detectIndent = require('detect-indent')
		@@ -3,0 +3,0 @@ const detectNewline = require('detect-newline')

package.json

		{
		"name": "commit-and-tag-version",
		"version": "11.2.0",
		"version": "11.2.1",
		"description": "replacement for `npm version` with automatic CHANGELOG generation",
		@@ -55,3 +55,2 @@ "bin": "bin/cli.js",
		"semver": "^7.1.1",
		"stringify-package": "^1.0.1",
		"yargs": "^17.0.0"
		@@ -58,0 +57,0 @@ },

README.md

		@@ -555,4 +555,30 @@ # Commit and Tag Version

		### Why do breaking changes before 1.0.0 not trigger a 1.0.0 release?

		Below 1.0.0, the semver specification doesn't give any guarantees about the
		meaning of version numbers. However, with npm there is a community convention,
		and implementation-defined behaviour: If your version is between 0.1.0 and
		1.0.0, npm treats an update to the minor version as a breaking change - that is
		^0.1.0 will match 0.1.2 but not 0.2.0. Rust's cargo package manager also behaves
		the same way.

		This tool (via conventional-commits) also follows that convention - breaking
		changes below v1.0.0 are treated as a minor version bump. Here's an example
		series of commits with tagged versions:

		```
		1017b00 chore: initial commit
		9e2ba95 (tag: v0.0.2) chore(release): 0.0.2
		3598012 fix!: Example breaking change
		1a4994a (tag: v0.1.0) chore(release): 0.1.0
		```

		Semver's only guarantee is "all bets are off", but npm has made a choice about
		what bets to make. `commit-and-tag-version` follows the same convention (along
		with other package managers for other ecosystems).

		When you are ready to release v1.0.0, add `--release-as 1.0.0` to the options.

		## License

		ISC

New alerts