package-versioner 0.8.1 → 0.8.3

package/README.md

@@ -74,7 +74,7 @@ npx package-versioner --dry-run --json
 
 By default, `package-versioner` intelligently handles Git tag reachability to provide the best user experience:
 
-- **Default behavior**: Uses reachable tags when available, but falls back to the latest repository tag if needed (common in feature branches)
+- **Default behaviour**: Uses reachable tags when available, but falls back to the latest repository tag if needed (common in feature branches)
 - **Strict mode (`--strict-reachable`)**: Only uses tags reachable from the current commit, following strict Git semantics
 
 This is particularly useful when working on feature branches that have diverged from the main branch where newer tags exist. The tool will automatically detect the Git context and provide helpful guidance:
@@ -151,13 +151,14 @@ Customize behaviour by creating a `version.config.json` file in your project roo
 - `updateChangelog`: Whether to automatically update changelogs (default: true)
 - `changelogFormat`: Format for changelogs - "keep-a-changelog" or "angular" (default: "keep-a-changelog")
 - `strictReachable`: Only use reachable tags, no fallback to unreachable tags (default: false)
+- `prereleaseIdentifier`: Identifier for prerelease versions (e.g., "alpha", "beta", "next") used in versions like "1.2.0-alpha.3"
 - `cargo`: Options for Rust projects:
   - `enabled`: Whether to handle Cargo.toml files (default: true)
   - `paths`: Directories to search for Cargo.toml files (optional)
 
 #### Monorepo-Specific Options
 - `synced`: Whether all packages should be versioned together (default: true)
-- `skip`: Array of package names to exclude from versioning
+- `skip`: Array of package names or patterns to exclude from versioning. Supports exact names, scope wildcards, path patterns, and global wildcards (e.g., ["@scope/package-a", "@scope/*", "packages/**/*"])
 - `packages`: Array of package names or patterns to target for versioning. Supports exact names, scope wildcards, and global wildcards (e.g., ["@scope/package-a", "@scope/*", "*"])
 - `mainPackage`: Package name whose commit history should drive version determination
 - `packageSpecificTags`: Whether to enable package-specific tagging behaviour (default: false)
@@ -167,7 +168,7 @@ For more details on CI/CD integration and advanced usage, see [CI/CD Integration
 
 ### Package Targeting
 
-The `packages` configuration option allows you to specify which packages should be processed for versioning. It supports several pattern types:
+The `packages` configuration option controls which packages are processed for versioning. It supports several pattern types:
 
 #### Exact Package Names
 ```json
@@ -200,7 +201,12 @@ Combine different pattern types:
 }
 ```
 
-**Note**: Package discovery is handled by your workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.). The `packages` option only filters which discovered packages to process.
+**Behaviour:**
+- When `packages` is specified, **only** packages matching those patterns will be processed
+- When `packages` is empty or not specified, **all** workspace packages will be processed  
+- The `skip` option can exclude specific packages from the selected set
+
+**Note**: Your workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.) determines which packages are available, but the `packages` option directly controls which ones get versioned.
 
 ### Package-Specific Tagging