JSPM – @techor/version@2.2.5

Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@techor/version) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Smartly bump all workspace-dependent packages to specific versions

Features

Synchronize versions of packages in all workspaces
Bump packages to a specific version by the .workspaces of package.json
Bump versions by analyzing dependencies and peerDependencies of the workspace
Prevent bumping versions for private: true packages

Getting Started

npm i @techor/version

Usage

techor version <version>
techor-version <version>

Check out the available options here for now

The command automatically bumps the version of all packages by scanning all workspaces and analyzing dependencies and peerDependencies of package.json

.
├── package.json
└── packages
    ├─── a
    |    └─── package.json
    ├─── b
    |    └─── package.json
    └─── c
         └─── package.json

This command scans all workspaces for dependencies with unspecified versions "" considered a project package, then replaces them with the next version.

Now bump all dependent and workspace packages to a specified version:

techor version 1.2.0

packages/a/package.json

{
    "name": "a",
+   "version": "^1.2.0",
    "dependencies": {
-       "b": "",
+       "b": "^1.2.0"
    }
}

packages/b/package.json

{
    "name": "b",
+   "version": "^1.2.0"
}

packages/c/package.json

{
    "name": "c",
+   "version": "^1.2.0",
    "peerDependencies": {
-       "a": "",
+       "b": "^1.2.0"
    }
}

For version range, check out the semver

Typically, you would use Aron's semantic release with CI to automate the version and release commands.