Navigation: Documentation Index · Configuration Reference · CLI Reference
This guide walks you through installing Versionings, creating a configuration file, and running your first release.
Before you begin, make sure you have the following installed:
- Node.js >= 18 — verify with
node -v - npm — verify with
npm -v - Git — verify with
git --version - An initialized Git repository with at least one remote configured (
git remote -v)
Install Versionings globally via npm:
npm install --global versioningsVerify the installation:
versionings doctorVersionings requires a configuration file that specifies your Git platform and repository URL. You can create one interactively or manually.
Run the init command to launch the interactive wizard:
versionings initThe wizard guides you through four steps:
- Git platform — choose your SCM platform (e.g.
github,bitbucket). - Repository URL — enter the HTTPS or SSH URL of your repository. If a remote named
originis detected, it is offered as the default. - PR target branch — specify the branch that pull requests should target (default:
main). - Config format — choose between
json(writesversion.json) andyaml(writes.versioningsrc.yml).
If a configuration file already exists, the wizard asks for confirmation before overwriting.
To skip the format prompt, pass --format:
versionings init --format=yamlFor a full list of init parameters, see the CLI Reference.
Create a version.json file in your project root with the minimum required fields:
{
"git": {
"platform": "github",
"url": "https://github.com/your-org/your-repo.git"
}
}Alternatively, create a .versioningsrc.yml file:
git:
platform: github
url: https://github.com/your-org/your-repo.gitBoth formats support the same fields. See the Configuration Reference for the complete list of options, default values, and environment variable overrides.
Before making any changes, preview what Versionings will do:
versionings plan --semver=patch --branch=initial-setupThe plan command performs a dry run — it shows the version bump, branch name, tag name, and all steps that would be executed, without modifying your repository.
When you are satisfied with the plan, run the release:
versionings release --semver=patch --branch=initial-setupThis bumps the version, creates a branch and tag, and commits the changes. Add --push to push to the remote and optionally open a pull request.
For the full list of release parameters and flags, see the CLI Reference.
Run the doctor command to verify that your environment and configuration are healthy:
versionings doctorA successful run confirms that Git is available, the repository has a valid remote, and the configuration file passes schema validation. If any issues are found, the doctor reports them with suggested fixes.
For details on exit codes and error handling, see the Failure Matrix.