package-versioner 0.8.1 → 0.8.3

package/docs/CI_CD_INTEGRATION.md

@@ -154,7 +154,7 @@ git push origin "v$NEW_VERSION"
 `package-versioner` 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 behavior
+- `CI=true`: Most CI environments set this automatically, which helps the tool adjust its output behaviour
 
 ## Skipping CI for Version Commits
 

package/docs/versioning.md

@@ -170,13 +170,6 @@ This dual support makes `package-versioner` suitable for both JavaScript/TypeScr
 
 When working with monorepos, you can control which packages are processed for versioning using the `packages` configuration option. This provides flexible targeting with support for various pattern types.
 
-### Package Discovery vs. Targeting
-
-It's important to understand the distinction:
-
-- **Package Discovery**: Handled by your workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.)
-- **Package Targeting**: Controlled by the `packages` option in version.config.json to filter which discovered packages to process
-
 ### Targeting Patterns
 
 #### Exact Package Names
@@ -205,13 +198,68 @@ Target all packages in the workspace:
 ```
 
 #### Mixed Patterns
-Combine different pattern types for flexible targeting:
+Target different types of packages using a combination of patterns:
 ```json
 {
   "packages": ["@mycompany/*", "@utils/logger", "legacy-package"]
 }
 ```
 
+### Skip Patterns
+
+The `skip` configuration option allows you to exclude specific packages from versioning using the same pattern matching capabilities as package targeting.
+
+#### Pattern Types
+
+1. **Exact Package Names**
+```json
+{
+  "skip": ["@internal/docs", "test-utils"]
+}
+```
+
+2. **Scope Wildcards**
+```json
+{
+  "skip": ["@internal/*"]
+}
+```
+This will skip all packages whose names start with `@internal/`.
+
+3. **Path Patterns**
+```json
+{
+  "skip": ["packages/**/test-*", "examples/**/*"]
+}
+```
+This will skip packages matching the specified path patterns.
+
+4. **Mixed Patterns**
+```json
+{
+  "skip": ["@internal/*", "test-*", "packages/examples/**/*"]
+}
+```
+
+#### Skip Pattern Priority
+
+Skip patterns take precedence over include patterns. If a package matches both a pattern in `packages` and a pattern in `skip`, it will be excluded from versioning.
+
+Example:
+```json
+{
+  "packages": ["@company/*"],
+  "skip": ["@company/internal-*"]
+}
+```
+In this case, all packages under the `@company` scope will be versioned except those starting with `@company/internal-`.
+
+### Behaviour
+
+- **When `packages` is specified**: Only packages matching those patterns will be processed for versioning
+- **When `packages` is empty or not specified**: All workspace packages will be processed
+- **Error handling**: If no packages match the specified patterns, a warning is displayed
+
 ### Excluding Packages
 
 Use the `skip` option to exclude specific packages from processing:
@@ -224,6 +272,8 @@ Use the `skip` option to exclude specific packages from processing:
 
 This configuration will process all packages in the `@mycompany` scope except for `@mycompany/deprecated-package`.
 
+**Note**: Your workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.) determines which packages are available in your workspace, but the `packages` option directly controls which ones get versioned.
+
 ## 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.
@@ -298,7 +348,7 @@ This would produce tags like `release-1.2.3` instead of `v1.2.3`.
   "packageSpecificTags": true
 }
 ```
-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`. 
 
 ### Behaviour in Different Modes
 

package/package-versioner.schema.json

@@ -21,7 +21,7 @@
     "packageSpecificTags": {
       "type": "boolean",
       "default": false,
-      "description": "Whether to enable package-specific tagging behavior"
+      "description": "Whether to enable package-specific tagging behaviour"
     },
     "preset": {
       "type": "string",
@@ -53,7 +53,7 @@
         "minLength": 1
       },
       "default": [],
-      "description": "Array of package names or patterns to target for versioning. Supports exact names (e.g., '@scope/package-a'), scope wildcards (e.g., '@scope/*'), and global wildcards (e.g., '*')"
+      "description": "Array of package names or patterns that determines which packages will be processed for versioning. When specified, only packages matching these patterns will be versioned. When empty or not specified, all workspace packages will be processed. Supports exact names (e.g., '@scope/package-a'), scope wildcards (e.g., '@scope/*'), and global wildcards (e.g., '*')"
     },
     "mainPackage": {
       "type": "string",
@@ -88,7 +88,7 @@
         "minLength": 1
       },
       "default": [],
-      "description": "Packages to exclude from versioning"
+      "description": "Packages to exclude from versioning. Supports exact package names (e.g., '@internal/docs'), scope wildcards (e.g., '@internal/*'), and path patterns (e.g., 'packages/**/test-*', 'examples/**/*')"
     },
     "commitMessage": {
       "type": "string",

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.8.1",
+  "version": "0.8.3",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",
@@ -37,29 +37,34 @@
     ]
   },
   "devDependencies": {
-    "@biomejs/biome": "^1.9.4",
+    "@biomejs/biome": "^2.0.6",
     "@types/figlet": "^1.5.5",
-    "@types/node": "^24.0.3",
+    "@types/node": "^24.0.10",
     "@types/semver": "^7.3.13",
-    "@vitest/coverage-v8": "^3.2.3",
+    "@vitest/coverage-v8": "^3.2.4",
+    "cross-env": "^7.0.3",
     "husky": "^9.1.7",
     "lint-staged": "^16.1.2",
     "tsup": "^8.5.0",
     "tsx": "^4.20.3",
     "typescript": "^5.8.3",
-    "vitest": "^3.2.3"
+    "vitest": "^3.2.4"
   },
   "dependencies": {
     "@manypkg/get-packages": "^3.0.0",
+    "@types/micromatch": "^4.0.9",
     "chalk": "^5.4.1",
     "commander": "^14.0.0",
     "conventional-changelog-angular": "^8.0.0",
+    "conventional-changelog-conventional-commits": "npm:conventional-changelog-conventionalcommits@^9.0.0",
+    "conventional-changelog-conventionalcommits": "^9.0.0",
     "conventional-commits-filter": "^5.0.0",
     "conventional-recommended-bump": "^11.2.0",
     "figlet": "^1.8.1",
     "git-semver-tags": "^8.0.0",
+    "micromatch": "^4.0.8",
     "semver": "^7.7.2",
-    "smol-toml": "^1.3.4"
+    "smol-toml": "^1.4.1"
   },
   "scripts": {
     "build": "tsup src/index.ts --format esm,cjs --dts",
@@ -67,7 +72,7 @@
     "clean": "rm -rf node_modules && rm -rf dist",
     "test": "pnpm run test:unit && pnpm run test:integration",
     "test:watch": "vitest --coverage",
-    "test:integration": "vitest --run --dir test/integration",
+    "test:integration": "pnpm run build && cross-env VITEST_INTEGRATION=true vitest --run --dir test/integration",
     "posttest:integration": "pnpm tsx scripts/cleanup-fixtures.ts",
     "test:unit": "vitest --run --coverage --dir test/unit",
     "lint": "biome check .",