package-versioner 0.5.1 → 0.5.2

package/README.md

@@ -87,7 +87,7 @@ Customize behavior by creating a `version.config.json` file in your project root
   "versionPrefix": "v",
   "tagTemplate": "${prefix}${version}",
   "packageTagTemplate": "${packageName}@${prefix}${version}",
-  "commitMessage": "chore(release): {{currentTag}} [skip ci]",
+  "commitMessage": "chore(release): ${version}",
   "monorepo": {
     "synced": true,
     "skip": [
@@ -99,7 +99,10 @@ Customize behavior by creating a `version.config.json` file in your project root
 }
 ```
 
-**Note:** Options like `synced`, `packages`, and `updateInternalDependencies` enable monorepo-specific behaviours. The `tagTemplate` and `packageTagTemplate` allow you to customize how Git tags are formatted for releases.
+**Notes:** 
+- Options like `synced`, `packages`, and `updateInternalDependencies` enable monorepo-specific behaviours.
+- The `tagTemplate` and `packageTagTemplate` allow you to customize how Git tags are formatted for releases.
+- The `commitMessage` template can include CI skip tokens like `[skip ci]` if you want to prevent CI runs after version commits (e.g., `"commitMessage": "chore(release): ${version} [skip ci]"`). See [CI/CD Integration](./docs/CI_CD_INTEGRATION.md) for more details.
 
 ## How Versioning Works
 

package/dist/index.cjs

@@ -758,7 +758,6 @@ var PackageProcessor = class {
     } else {
       commitMessage = `chore(release): ${packageNames} ${representativeVersion}`;
     }
-    commitMessage += " [skip-ci]";
     setCommitMessage(commitMessage);
     if (!this.dryRun) {
       try {

package/dist/index.js

@@ -734,7 +734,6 @@ var PackageProcessor = class {
     } else {
       commitMessage = `chore(release): ${packageNames} ${representativeVersion}`;
     }
-    commitMessage += " [skip-ci]";
     setCommitMessage(commitMessage);
     if (!this.dryRun) {
       try {

package/docs/CI_CD_INTEGRATION.md

@@ -156,6 +156,24 @@ git push origin "v$NEW_VERSION"
 - `NO_COLOR=1`: Disables colored output in logs (automatically detected in CI environments)
 - `CI=true`: Most CI environments set this automatically, which helps the tool adjust its output behavior
 
+## Skipping CI for Version Commits
+
+If you want to prevent additional CI runs when version commits are made, you can include CI skip flags in your commit message template in `version.config.json`:
+
+```json
+{
+  "commitMessage": "chore(release): ${version} [skip ci]",
+  // other configuration options...
+}
+```
+
+Common CI skip patterns include:
+- `[skip ci]` or `[ci skip]` - Works in GitHub Actions, GitLab CI, CircleCI
+- `[skip-ci]` - Alternative format supported by some CI systems
+- `[no ci]` - Another variant 
+
+Each CI system might have slightly different syntax, so check your CI provider's documentation for the exact skip token to use.
+
 ## Tips for Reliable CI/CD Integration
 
 1. **Always use `--json`** in CI/CD pipelines for consistent output parsing

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "package-versioner",
   "description": "A lightweight yet powerful CLI tool for automated semantic versioning based on Git history and conventional commits.",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",