@reiniiriarios/newver

🔥 newver

A silly little script to help quickly update a version in package files, then commit, tag, and push. Useful when, like me, you use tagged releases and push versions manually and frequently.

CLI Usage

newver <version> [options]
newver 1.2.3
newver 1.2.3 -c
newver 1.2.3 --commit
newver 1.2.3 --commit=true --tag=false --push=true --prefix="chore(release)"
newver 1.2.3 -cptx "chore(release)"
newver 1.2.3 --files=path/to/file.ext --files=path/to/another/file.ext

{
  "scripts": {
    "bump": "newver --commit=true"
  }
}

npm run bump 1.2.3

For option details:

newver --help

Example output

$ newver --commit=false 1.2.3
Updating version to 1.2.3
▸ package.json updated
▸ package-lock.json updated

$ newver --commit=false 1.0.0
Updating version to 1.0.0
▸ Version 1.0.0 is older than version 1.2.3 in package.json. Proceed? (Y/n) y
▸ package.json updated
▸ Version 1.0.0 is older than version 1.2.3 in package-lock.json. Proceed? (Y/n) y
▸ package-lock.json updated

Script Usage

#!/usr/bin/env node
import newver from "newver";

newver(process.args.pop(), {
  quiet: true,
  commit: true,
  prefix: "chore(release)",
  files: ["package.json", "package-lock.json", "path/to/another/file.json"],
});

Supported data formats

• .json
• .yaml / .yml
• .toml

Other formats are find-and-replace.

Supported auto-magical files

These will be looked for automatically in the project's root directory. Other files may be specified manually.

• package.json
• package-lock.json
• Cargo.toml
• snapcraft.yaml
• wails.json
• go.mod