revola.json
Configuration file for Revola
| Type | object |
|---|---|
| File match |
.revola.json
.revola.config.json
revola.json
revola.config.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/revola-json/latest.json |
| Source | https://www.schemastore.org/revola.json |
Validate with Lintel
npx @lintel/lintel check
Configuration file for Revola
Properties
Path to the JSON schema for IDE autocompletion.
Controls the verbosity of Revola logging output.
Preset configuration allowing a single value or a unique array values.
Configuration for versioning behavior.
{
"strategy": "semver",
"defaultBump": "patch"
}
2 nested properties
Determines how the next version is calculated.
The default level to bump the version when using the "semver" strategy.
Configuration for Git-related settings in Revola.
{
"cleanWorkingDirectory": true,
"upstream": true,
"author": {
"name": "github-actions[bot]",
"email": "41898282+github-actions[bot]@users.noreply.github.com"
},
"targetBranch": "main",
"add": true,
"commit": true,
"commitMessage": "Release {{REVOLA_VERSION}}",
"push": true,
"tag": true,
"tagFormat": "v{{REVOLA_VERSION}}",
"tagAnnotation": "Release {{REVOLA_VERSION}}",
"tagMajor": false,
"tagMinor": false
}
13 nested properties
If true, Revola will check for a clean working directory before performing versioning operations.
If true, Revola will check for an upstream branch and push to it by default when pushing new versions.
Overrides Git author identity ONLY for release commits (does not modify global Git config).
{
"name": "github-actions[bot]",
"email": "41898282+github-actions[bot]@users.noreply.github.com"
}
2 nested properties
Name to use for release commits.
Email to use for release commits.
The branch on which to perform versioning operations.
If true, Revola will stage all changes before committing the new version.
If true, Revola will commit the new version.
If true, Revola will push the new version to the remote repository.
If true, Revola will create a Git tag for the new version (e.g: v1.2.3).
Template for Git tag names.
The annotation to use for Git tags created by Revola.
If true, Revola will create a Git tag for major version releases (e.g: v1.2.3 -> v1).
If true, Revola will create a Git tag for minor version releases (e.g: v1.2.3 -> v1.2).
npm publish configuration
{
"publish": true,
"registry": "https://registry.npmjs.org/",
"tokenRef": "NPM_TOKEN",
"packageManager": "npm",
"tag": "latest",
"access": "public",
"provenance": false
}
7 nested properties
Whether to publish to npm.
The npm registry URL to publish to.
Environment variable name that holds the registry auth token.
The package manager used to invoke the npm publish command.
The dist-tag to publish under (e.g. latest, next, beta).
Package access level on npm.
Whether to publish with npm provenance (requires CI environment).
jsr publish configuration
{
"publish": false,
"tokenRef": "JSR_TOKEN",
"packageManager": "npx"
}
4 nested properties
Whether to publish to JSR.
Additional arguments to pass to the JSR publish command.
Environment variable name that holds the registry auth token (e.g. "JSR_TOKEN").
The package manager used to invoke the JSR publish command.
Changelog configuration
{
"enabled": true,
"file": "CHANGELOG.md",
"title": "{{REVOLA_VERSION}} ({{REVOLA_DATE}})",
"includeTypes": [
"BREAKING CHANGE",
"feat",
"fix",
"perf",
"refactor",
"docs",
"deps",
"ci",
"chore"
]
}
4 nested properties
Whether to generate/update the changelog.
Path to the changelog file.
Template for release title.
List of commit types to include in the changelog. If empty or not provided, all commit types are included. The order matters and determines how sections are organized in the final changelog.
[
"BREAKING CHANGE",
"feat",
"fix",
"perf",
"refactor",
"docs",
"deps",
"ci",
"chore"
]
Shell commands to run at various lifecycle stages. Each key is a lifecycle hook name and the value is the command(s) to run.
Defines plugins where each key is a plugin name and the value is its configuration object.