package-versioner 0.5.3 → 0.6.0

package/docs/VERSIONING_STRATEGIES.md

@@ -134,6 +134,35 @@ This applies to all standard bump types:
 - `--bump minor`: 1.0.0-beta.1 -> 1.1.0 
 - `--bump patch`: 1.0.0-beta.1 -> 1.0.1
 
+## Package Type Support
+
+`package-versioner` supports both JavaScript/TypeScript projects using `package.json` and Rust projects using `Cargo.toml`:
+
+### JavaScript/TypeScript Projects
+
+For JavaScript/TypeScript projects, the tool looks for and updates the `version` field in `package.json` files according to the versioning strategies described above.
+
+### Rust Projects
+
+For Rust projects, the tool looks for and updates the `package.version` field in `Cargo.toml` files using the same versioning strategies.
+
+When no tags are found for a project, `package-versioner` will:
+1. Look for the `version` in `package.json` if it exists
+2. Look for the `package.version` in `Cargo.toml` if it exists
+3. Fall back to the configured `initialVersion` (default: "0.1.0")
+
+### Mixed Projects with Both Manifests
+
+When both `package.json` and `Cargo.toml` exist in the same directory, `package-versioner` 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)
+3. Fall back to checking `Cargo.toml` only if `package.json` doesn't exist or doesn't have a version
+
+This allows you to maintain consistent versioning across JavaScript and Rust components in the same package.
+
+This dual support makes `package-versioner` suitable for both JavaScript/TypeScript and Rust repositories, as well as monorepos or projects containing both types of packages.
+
 ## 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.
@@ -184,4 +213,4 @@ This would produce tags like `release-1.2.3` instead of `v1.2.3`.
   "packageTagTemplate": "${packageName}-${prefix}${version}"
 }
 ```
-This would produce package tags like `@scope/package-name-v1.2.3` instead of `@scope/package-name@v1.2.3`.
+This would produce package tags like `@scope/package-name-v1.2.3` instead of `@scope/package-name@v1.2.3`.

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.3",
+  "version": "0.6.0",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",
@@ -32,31 +32,33 @@
   },
   "lint-staged": {
     "*.{js,ts,jsx,tsx}": [
-      "biome check --apply",
+      "biome check --write",
       "biome format --write"
     ]
   },
   "devDependencies": {
     "@biomejs/biome": "^1.9.4",
     "@types/figlet": "^1.5.5",
-    "@types/node": "^22.14.1",
+    "@types/node": "^22.15.3",
     "@types/semver": "^7.3.13",
-    "@vitest/coverage-v8": "^3.1.1",
+    "@vitest/coverage-v8": "^3.1.2",
     "husky": "^9.1.7",
     "lint-staged": "^15.5.1",
     "tsup": "^8.4.0",
     "typescript": "^5.8.3",
-    "vitest": "^3.1.1"
+    "vitest": "^3.1.2"
   },
   "dependencies": {
-    "@manypkg/get-packages": "^2.2.2",
+    "@manypkg/get-packages": "^3.0.0",
     "chalk": "^5.4.1",
     "commander": "^13.1.0",
     "conventional-changelog-angular": "^8.0.0",
+    "conventional-commits-filter": "^5.0.0",
     "conventional-recommended-bump": "^11.0.0",
     "figlet": "^1.8.1",
     "git-semver-tags": "^8.0.0",
-    "semver": "^7.7.1"
+    "semver": "^7.7.1",
+    "smol-toml": "^1.3.4"
   },
   "scripts": {
     "build": "tsup src/index.ts --format esm,cjs --dts",
@@ -65,7 +67,7 @@
     "test": "vitest run --coverage",
     "test:watch": "vitest --coverage",
     "lint": "biome check .",
-    "lint:fix": "biome check --apply .",
+    "lint:fix": "biome check --write .",
     "format": "biome format --write .",
     "format:check": "biome format .",
     "fix": "pnpm run lint:fix && pnpm run format"