@releasekit/version 0.3.0-next.4 → 0.3.0

package/README.md

@@ -22,6 +22,8 @@ npm install -g @releasekit/version
 pnpm add -g @releasekit/version
 ```
 
+> **Note:** This package is ESM only and requires Node.js 20+.
+
 ## Quick Start
 
 ```bash
@@ -82,7 +84,7 @@ When using `--json`, the tool outputs structured data including version bumps an
       ]
     }
   ],
-  "commitMessage": "chore(release): v1.2.3",
+  "commitMessage": "chore: release v1.2.3",
   "tags": ["v1.2.3"]
 }
 ```
@@ -99,7 +101,7 @@ Configure via `releasekit.config.json`:
     "preset": "conventionalcommits",
     "versionPrefix": "v",
     "tagTemplate": "${prefix}${version}",
-    "commitMessage": "chore(release): v${version}",
+    "commitMessage": "chore: release ${packageName} v${version}",
     "sync": true,
     "packages": ["@mycompany/*"],
     "skip": ["docs", "e2e"],
@@ -121,7 +123,7 @@ Configure via `releasekit.config.json`:
 | `preset` | Conventional commits preset | `"conventionalcommits"` |
 | `versionPrefix` | Tag version prefix | `"v"` |
 | `tagTemplate` | Git tag template | `"${prefix}${version}"` |
-| `commitMessage` | Commit message template | `"chore(release): ${version}"` |
+| `commitMessage` | Commit message template | `"chore: release ${packageName} v${version}"` |
 | `sync` | Version all packages together | `false` |
 | `packages` | Package name patterns to include | all |
 | `skip` | Package name patterns to exclude | `[]` |

package/dist/cli.js

@@ -1,106 +1 @@
 #!/usr/bin/env node
-import {
-  VersionEngine,
-  enableJsonOutput,
-  loadConfig,
-  log,
-  printJsonOutput
-} from "./chunk-ZEXPJ53Z.js";
-import "./chunk-GQLJ7JQY.js";
-import "./chunk-LMPZV35Z.js";
-
-// src/cli.ts
-import * as fs from "fs";
-import path from "path";
-import { Command } from "commander";
-function getPackageVersion() {
-  try {
-    const packageJsonPath = path.resolve(path.dirname(import.meta.url.replace("file:", "")), "../package.json");
-    const packageJsonContent = fs.readFileSync(packageJsonPath, "utf-8");
-    const packageJson = JSON.parse(packageJsonContent);
-    return packageJson.version || "0.0.0";
-  } catch (error) {
-    console.error("Failed to read package version:", error);
-    return "0.0.0";
-  }
-}
-async function main() {
-  const program = new Command();
-  program.name("releasekit-version").description("Version a package or packages based on conventional commits").version(getPackageVersion()).command("version", { isDefault: true }).description("Version a package or packages based on configuration").option("-c, --config <path>", "Path to config file (defaults to releasekit.config.json in current directory)").option("-d, --dry-run", "Dry run (no changes made)", false).option("-b, --bump <type>", "Specify bump type (patch|minor|major)").option("-p, --prerelease [identifier]", "Create prerelease version").option("-s, --sync", "Use synchronized versioning across all packages").option("-j, --json", "Output results as JSON", false).option("-t, --target <packages>", "Comma-delimited list of package names to target").option("--project-dir <path>", "Project directory to run commands in", process.cwd()).action(async (options) => {
-    if (options.json) {
-      enableJsonOutput(options.dryRun);
-    }
-    try {
-      const originalCwd = process.cwd();
-      if (options.projectDir && options.projectDir !== originalCwd) {
-        try {
-          process.chdir(options.projectDir);
-          log(`Changed working directory to: ${options.projectDir}`, "debug");
-        } catch (error) {
-          throw new Error(
-            `Failed to change to directory "${options.projectDir}": ${error instanceof Error ? error.message : String(error)}`
-          );
-        }
-      }
-      const config = loadConfig({ cwd: options.projectDir, configPath: options.config });
-      log(`Loaded configuration from ${options.config || "releasekit.config.json"}`, "info");
-      if (options.dryRun) config.dryRun = true;
-      if (options.sync) config.sync = true;
-      if (options.bump) config.type = options.bump;
-      if (options.prerelease) {
-        config.prereleaseIdentifier = options.prerelease === true ? "next" : options.prerelease;
-        config.isPrerelease = true;
-      }
-      const cliTargets = options.target ? options.target.split(",").map((t) => t.trim()) : [];
-      if (cliTargets.length > 0) {
-        config.packages = cliTargets;
-        log(`CLI targets specified: ${cliTargets.join(", ")}`, "info");
-      }
-      const engine = new VersionEngine(config, !!options.json);
-      const pkgsResult = await engine.getWorkspacePackages();
-      const resolvedCount = pkgsResult.packages.length;
-      log(`Resolved ${resolvedCount} packages from workspace`, "debug");
-      log(`Config packages: ${JSON.stringify(config.packages)}`, "debug");
-      log(`Config sync: ${config.sync}`, "debug");
-      if (config.sync) {
-        log("Using sync versioning strategy.", "info");
-        engine.setStrategy("sync");
-        await engine.run(pkgsResult);
-      } else if (resolvedCount === 1) {
-        log("Using single package versioning strategy.", "info");
-        if (cliTargets.length > 0) {
-          log("--target flag is ignored for single package strategy.", "warning");
-        }
-        engine.setStrategy("single");
-        await engine.run(pkgsResult);
-      } else if (resolvedCount === 0) {
-        throw new Error("No packages found in workspace");
-      } else {
-        log("Using async versioning strategy.", "info");
-        if (cliTargets.length > 0) {
-          log(`Targeting specific packages: ${cliTargets.join(", ")}`, "info");
-        }
-        engine.setStrategy("async");
-        await engine.run(pkgsResult, cliTargets);
-      }
-      log("Versioning process completed.", "success");
-      printJsonOutput();
-    } catch (error) {
-      const { BaseVersionError } = await import("./baseError-ZCZHF6A2.js");
-      if (BaseVersionError.isVersionError(error)) {
-        error.logError();
-      } else {
-        log(`Error: ${error instanceof Error ? error.message : String(error)}`, "error");
-      }
-      process.exit(1);
-    }
-  });
-  program.parse();
-}
-async function run() {
-  await main();
-}
-main();
-export {
-  run
-};

package/docs/CI_CD_INTEGRATION.md

@@ -1,17 +1,17 @@
 # CI/CD Integration
 
-`package-versioner` is designed to work seamlessly in CI/CD pipelines, making it easy to automate versioning as part of your release workflow.
+`releasekit-version` is designed to work seamlessly in CI/CD pipelines, making it easy to automate versioning as part of your release workflow.
 
 ## JSON Output Mode
 
-For programmatic consumption in CI/CD scripts, `package-versioner` provides a structured JSON output option:
+For programmatic consumption in CI/CD scripts, `releasekit-version` provides a structured JSON output option:
 
 ```bash
 # Output results in JSON format
-npx package-versioner --json
+npx releasekit-version --json
 
 # Combine with dry-run for planning
-npx package-versioner --dry-run --json
+npx releasekit-version --dry-run --json
 ```
 
 This will suppress all normal console output and instead output a single JSON object containing:
@@ -39,7 +39,7 @@ This will suppress all normal console output and instead output a single JSON ob
       ]
     }
   ],
-  "commitMessage": "chore(release): v1.2.3", // The commit message that was used
+  "commitMessage": "chore: release my-package v1.2.3", // The commit message that was used
   "tags": [                                  // Array of tags that were created
     "v1.2.3"                                 // or package-specific tags in targeted mode
   ]
@@ -58,7 +58,7 @@ The structured JSON output provides several advantages for CI/CD integration:
 
 ## Sample CI/CD Integration Patterns
 
-Here are some common ways to incorporate `package-versioner` into your CI/CD pipeline:
+Here are some common ways to incorporate `releasekit-version` into your CI/CD pipeline:
 
 ### GitHub Actions Workflow Example
 
@@ -77,12 +77,12 @@ jobs:
       new_version: ${{ steps.version.outputs.new_version }}
     
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v6
         with:
           fetch-depth: 0  # Important for git history
       
       - name: Setup Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v6
         with:
           node-version: '18'
           
@@ -93,7 +93,7 @@ jobs:
         id: version
         run: |
           # Run in JSON mode for parsing
-          VERSION_OUTPUT=$(npx package-versioner --json)
+          VERSION_OUTPUT=$(npx releasekit-version --json)
           echo "Version output: $VERSION_OUTPUT"
           
           # Use jq to parse the JSON output
@@ -127,7 +127,7 @@ determine_version:
   script:
     - npm ci
     - |
-      VERSION_OUTPUT=$(npx package-versioner --json)
+      VERSION_OUTPUT=$(npx releasekit-version --json)
       echo "VERSION_OUTPUT=$VERSION_OUTPUT" >> version.env
       
       # Parse values for use in later stages
@@ -153,7 +153,7 @@ publish:
 
 ## Working with Tags in CI
 
-When using the targeted mode with `-t` flag, `package-versioner` creates package-specific tags (e.g., `@scope/package-a@1.2.0`) but not a global tag. If your release process needs a global tag, you can add a step to your CI/CD pipeline:
+When using the targeted mode with `-t` flag, `releasekit-version` creates package-specific tags (e.g., `@scope/package-a@1.2.0`) but not a global tag. If your release process needs a global tag, you can add a step to your CI/CD pipeline:
 
 ```bash
 # Create a global tag based on the representative version
@@ -164,7 +164,7 @@ git push origin "v$NEW_VERSION"
 
 ## Environment Variables
 
-`package-versioner` respects the following environment variables:
+`releasekit-version` respects the following environment variables:
 
 - `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 behaviour
@@ -175,7 +175,7 @@ If you want to prevent additional CI runs when version commits are made, you can
 
 ```json
 {
-  "commitMessage": "chore(release): ${version} [skip ci]",
+  "commitMessage": "chore: release ${packageName} v${version} [skip ci]",
   // other configuration options...
 }
 ```

package/docs/versioning.md

@@ -1,6 +1,6 @@
 # Versioning Strategies and Concepts
 
-`package-versioner` offers flexible ways to determine the next version for your project based on its history and your configuration.
+`releasekit-version` offers flexible ways to determine the next version for your project based on its history and your configuration.
 
 ## How the Next Version is Calculated
 
@@ -8,7 +8,7 @@ There are two primary methods the tool uses to decide the version bump (e.g., pa
 
 ### 1. Conventional Commits (`versionStrategy: "conventional"`)
 
-This is the default strategy. `package-versioner` analyzes Git commit messages since the last Git tag that follows semver patterns. It uses the [conventional-commits](https://www.conventionalcommits.org/) specification to determine the bump:
+This is the default strategy. `releasekit-version` analyzes Git commit messages since the last Git tag that follows semver patterns. It uses the [conventional-commits](https://www.conventionalcommits.org/) specification to determine the bump:
 
 -   **Patch Bump (e.g., 1.2.3 -> 1.2.4):** Triggered by `fix:` commit types.
 -   **Minor Bump (e.g., 1.2.3 -> 1.3.0):** Triggered by `feat:` commit types.
@@ -67,7 +67,7 @@ This allows you to enforce version bumps based on your branching workflow (e.g.,
 
 ## Package Type Support
 
-`package-versioner` supports both JavaScript/TypeScript projects using `package.json` and Rust projects using `Cargo.toml`:
+`releasekit-version` supports both JavaScript/TypeScript projects using `package.json` and Rust projects using `Cargo.toml`:
 
 ### JavaScript/TypeScript Projects
 
@@ -79,7 +79,7 @@ For Rust projects, the tool looks for and updates the `package.version` field in
 
 ### Mixed Projects with Both Manifests
 
-When both `package.json` and `Cargo.toml` exist in the same directory, `package-versioner` will:
+When both `package.json` and `Cargo.toml` exist in the same directory, `releasekit-version` will:
 
 1. Update both manifest files independently with the same calculated version
 2. First check `package.json` for the current version (when no tags exist)
@@ -89,7 +89,7 @@ This allows you to maintain consistent versioning across JavaScript and Rust com
 
 ## Version Source Selection
 
-`package-versioner` uses a smart version source selection strategy to determine the base version for calculating the next version:
+`releasekit-version` uses a smart version source selection strategy to determine the base version for calculating the next version:
 
 1. First, it checks for Git tags:
    - In normal mode: Uses the latest reachable tag, falling back to unreachable tags if needed
@@ -273,7 +273,7 @@ This configuration will process all packages in the `@mycompany` scope except fo
 
 ## Tag Templates and Configuration
 
-`package-versioner` provides flexible configuration for how Git tags are formatted, allowing you to customize the tag structure for both single package repositories and monorepos.
+`releasekit-version` provides flexible configuration for how Git tags are formatted, allowing you to customize the tag structure for both single package repositories and monorepos.
 
 ### Tag Template Configuration
 
@@ -355,7 +355,7 @@ This would produce package tags like `@scope/package-name-v1.2.3` instead of `@s
 
 ## Troubleshooting Template Configuration
 
-`package-versioner` provides helpful warnings when template configurations don't match your project setup. Here are common issues and their solutions:
+`releasekit-version` provides helpful warnings when template configurations don't match your project setup. Here are common issues and their solutions:
 
 ### Template Contains ${packageName} but No Package Name Available
 
@@ -430,7 +430,7 @@ For global commit messages, use templates without `${packageName}`:
 
 ## Monorepo Versioning Modes
 
-While primarily used for single packages now, `package-versioner` retains options for monorepo workflows, controlled mainly by the `sync` flag in `version.config.json`.
+While primarily used for single packages now, `releasekit-version` retains options for monorepo workflows, controlled mainly by the `sync` flag in `version.config.json`.
 
 ### Sync Mode (`sync: true`)
 
@@ -457,13 +457,13 @@ This is the default if the `sync` flag is present and true.
     -   It calculates an appropriate version bump **independently for each targeted package** based on its commit history.
     -   The `package.json` file of each successfully updated targeted package is modified.
     -   An **individual Git tag** (e.g., `packageName@1.2.3`) is created **for each successfully updated package** immediately after its version is bumped.
-    -   Finally, a **single commit** is created including all the updated `package.json` files, using a summary commit message (e.g., `chore(release): pkg-a, pkg-b 1.2.3 [skip-ci]`).
-    -   **Important:** Only package-specific tags are created. The global tag (e.g., `v1.2.3`) is **not** automatically generated in this mode. If your release process (like GitHub Releases) depends on a global tag, you'll need to create it manually in your CI/CD script *after* `package-versioner` completes.
+    -   Finally, a **single commit** is created including all the updated `package.json` files, using a summary commit message (e.g., `chore: release pkg-a, pkg-b v1.2.3 [skip ci]`).
+    -   **Important:** Only package-specific tags are created. The global tag (e.g., `v1.2.3`) is **not** automatically generated in this mode. If your release process (like GitHub Releases) depends on a global tag, you'll need to create it manually in your CI/CD script *after* `releasekit-version` completes.
 -   **Use Case:** Releasing specific packages independently while still tagging each released package individually.
 
 ## Prerelease Handling
 
-`package-versioner` provides flexible handling for prerelease versions, allowing both creation of prereleases and promotion to stable releases.
+`releasekit-version` provides flexible handling for prerelease versions, allowing both creation of prereleases and promotion to stable releases.
 
 ### Creating Prereleases
 
@@ -471,7 +471,7 @@ Use the `--prerelease` flag with an identifier to create a prerelease version:
 
 ```bash
 # Create a beta prerelease
-npx package-versioner --bump minor --prerelease beta
+npx releasekit-version --bump minor --prerelease beta
 # Result: 1.0.0 -> 1.1.0-beta.0
 ```
 
@@ -485,11 +485,11 @@ You can also set a default prerelease identifier in your `version.config.json`:
 
 ### Promoting Prereleases to Stable Releases
 
-When using standard bump types (`major`, `minor`, `patch`) with the `--bump` flag on a prerelease version, `package-versioner` will automatically clean the prerelease identifier:
+When using standard bump types (`major`, `minor`, `patch`) with the `--bump` flag on a prerelease version, `releasekit-version` will automatically clean the prerelease identifier:
 
 ```bash
 # Starting from version 1.0.0-beta.1
-npx package-versioner --bump major
+npx releasekit-version --bump major
 # Result: 1.0.0-beta.1 -> 2.0.0 (not 2.0.0-beta.0)
 ```
 

package/package.json

@@ -1,9 +1,8 @@
 {
   "name": "@releasekit/version",
-  "version": "0.3.0-next.4",
+  "version": "0.3.0",
   "description": "Semantic versioning based on Git history and conventional commits",
   "type": "module",
-  "main": "./dist/index.cjs",
   "module": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {
@@ -11,10 +10,12 @@
       "import": {
         "types": "./dist/index.d.ts",
         "default": "./dist/index.js"
-      },
-      "require": {
-        "types": "./dist/index.d.cts",
-        "default": "./dist/index.cjs"
+      }
+    },
+    "./cli": {
+      "import": {
+        "types": "./dist/cli.d.ts",
+        "default": "./dist/cli.js"
       }
     }
   },
@@ -59,9 +60,8 @@
     "git-semver-tags": "^8.0.1",
     "micromatch": "^4.0.8",
     "semver": "^7.7.4",
-    "smol-toml": "^1.6.0",
-    "@releasekit/config": "0.1.0",
-    "@releasekit/core": "0.1.0"
+    "smol-toml": "^1.6.1",
+    "zod": "^4.3.6"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.4.6",
@@ -71,14 +71,16 @@
     "@vitest/coverage-v8": "^4.1.0",
     "tsup": "^8.5.1",
     "typescript": "^5.9.3",
-    "vitest": "^4.1.0"
+    "vitest": "^4.1.0",
+    "@releasekit/core": "0.0.0",
+    "@releasekit/config": "0.0.0"
   },
   "engines": {
     "node": ">=20"
   },
   "scripts": {
-    "build": "tsup src/index.ts src/cli.ts --format esm,cjs --dts",
-    "dev": "tsup src/index.ts src/cli.ts --format esm,cjs --watch --dts",
+    "build": "tsup",
+    "dev": "tsup --watch",
     "clean": "rm -rf dist coverage .turbo",
     "test": "vitest run --dir test/unit",
     "test:unit": "vitest run --coverage --dir test/unit",

package/version.schema.json

@@ -93,7 +93,7 @@
     "commitMessage": {
       "type": "string",
       "minLength": 1,
-      "default": "chore(release): v${version}",
+      "default": "chore: release ${packageName} v${version}",
       "description": "Template for commit messages. Available variables: ${version}, ${packageName}, ${scope}"
     },
     "prereleaseIdentifier": {

package/dist/baseError-ZCZHF6A2.js

@@ -1,7 +0,0 @@
-import {
-  BaseVersionError
-} from "./chunk-GQLJ7JQY.js";
-export {
-  BaseVersionError as BasePackageVersionerError,
-  BaseVersionError
-};

package/dist/chunk-GQLJ7JQY.js

@@ -1,18 +0,0 @@
-// src/errors/baseError.ts
-import { ReleaseKitError } from "@releasekit/core";
-var BaseVersionError = class _BaseVersionError extends ReleaseKitError {
-  code;
-  suggestions;
-  constructor(message, code, suggestions) {
-    super(message);
-    this.code = code;
-    this.suggestions = suggestions ?? [];
-  }
-  static isVersionError(error) {
-    return error instanceof _BaseVersionError;
-  }
-};
-
-export {
-  BaseVersionError
-};

package/dist/chunk-LMPZV35Z.js

@@ -1,20 +0,0 @@
-// src/git/commandExecutor.ts
-import { execFile, execFileSync } from "child_process";
-var execAsync = (file, args, options) => {
-  const defaultOptions = { maxBuffer: 1024 * 1024 * 10, ...options };
-  return new Promise((resolve, reject) => {
-    execFile(file, args, defaultOptions, (error, stdout, stderr) => {
-      if (error) {
-        reject(error);
-      } else {
-        resolve({ stdout: stdout.toString(), stderr: stderr.toString() });
-      }
-    });
-  });
-};
-var execSync = (file, args, options) => execFileSync(file, args, { maxBuffer: 1024 * 1024 * 10, ...options });
-
-export {
-  execAsync,
-  execSync
-};