autorel 2.6.6 → 2.6.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -269,7 +269,7 @@ autorel --publish --run 'npm version ${NEXT_VERSION} --no-git-tag-version && doc
|
|
|
269
269
|
|
|
270
270
|
**Why this approach?**
|
|
271
271
|
- The version in `package.json` is only needed for npm publishing
|
|
272
|
-
- Committing version changes can cause merge conflicts
|
|
272
|
+
- Committing version changes can cause merge conflicts and create unnecessary noise in your repository
|
|
273
273
|
- The git tag is the source of truth for your version
|
|
274
274
|
- Package.json is automatically restored, so there's nothing to rollback
|
|
275
275
|
|
|
@@ -292,7 +292,7 @@ Here are examples of commit messages and the resulting version bump (using defau
|
|
|
292
292
|
By default, the following commit types trigger releases:
|
|
293
293
|
- `feat`: minor version bump
|
|
294
294
|
- `fix`, `perf`, `revert`: patch version bump
|
|
295
|
-
- `feat
|
|
295
|
+
- Any commit with `!` after the type (e.g., `feat!:`) or `BREAKING CHANGE:`/`BREAKING CHANGES:` in the footer: major version bump
|
|
296
296
|
|
|
297
297
|
Other commit types (like `docs`, `style`, `refactor`, `test`, `build`, `ci`) don't trigger releases but are included in changelogs.
|
|
298
298
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "autorel",
|
|
3
|
-
"version": "2.6.
|
|
3
|
+
"version": "2.6.8",
|
|
4
4
|
"description": "Automate semantic releases based on conventional commits. Similar to semantic-release but much simpler.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "Marc H. Weiner <mhweiner234@gmail.com> (https://mhweiner.com)",
|