revola.json
Configuration file for Revola
.revola.json.revola.config.jsonrevola.jsonrevola.config.json
Validate
Check your file against this schema
Opens the validator with this schema already loaded. Paste your
.revola.json and it validates in your browser — nothing is uploaded.
Reference
Fields
Generated directly from the schema, following local
$refs, to two levels of nesting.
| Field | Type | Description |
|---|---|---|
$schema | string | Path to the JSON schema for IDE autocompletion. default: "https://cdn.jsdelivr.net/npm/revola@0.1.0/schema.json" |
logLevel | string | Controls the verbosity of Revola logging output. default: "info"one of: "trace", "debug", "info", "success", "warn", "error" … (+2) |
preset | anyOf | Preset configuration allowing a single value or a unique array values. default: "node" |
version | object | Configuration for versioning behavior. default: {"strategy": "semver", "defaultBump": "patch"} |
version.strategy | string | Determines how the next version is calculated. default: "semver"one of: "semver" |
version.defaultBump | string | The default level to bump the version when using the "semver" strategy. default: "patch" |
git | object | Configuration for Git-related settings in Revola. default: {"cleanWorkingDirectory": true, "upstream": true, "author"… |
git.cleanWorkingDirectory | boolean | If true, Revola will check for a clean working directory before performing versioning operations. default: true |
git.upstream | boolean | If true, Revola will check for an upstream branch and push to it by default when pushing new versions. default: true |
git.author | object | Overrides Git author identity ONLY for release commits (does not modify global Git config). default: {"name": "github-actions[bot]", "email"… |
git.author.name | string | Name to use for release commits. default: "github-actions[bot]" |
git.author.email | string | Email to use for release commits. default: "41898282+github-actions[bot]@users.noreply.github.com" |
git.targetBranch | string | The branch on which to perform versioning operations. default: "main" |
git.add | boolean | If true, Revola will stage all changes before committing the new version. default: true |
git.commit | boolean | If true, Revola will commit the new version. default: true |
git.commitMessage | string | — default: "Release {{REVOLA_VERSION}}" |
git.push | boolean | If true, Revola will push the new version to the remote repository. default: true |
git.tag | boolean | If true, Revola will create a Git tag for the new version (e.g: v1.2.3). default: true |
git.tagFormat | string | Template for Git tag names. default: "v{{REVOLA_VERSION}}" |
git.tagAnnotation | string | The annotation to use for Git tags created by Revola. default: "Release {{REVOLA_VERSION}}" |
git.tagMajor | boolean | If true, Revola will create a Git tag for major version releases (e.g: v1.2.3 -> v1). default: false |
git.tagMinor | boolean | If true, Revola will create a Git tag for minor version releases (e.g: v1.2.3 -> v1.2). default: false |
npm | object | npm publish configuration default: {"publish": true, "registry": "https://registry.npmjs.org/"… |
npm.publish | boolean | Whether to publish to npm. default: true |
npm.registry | string | The npm registry URL to publish to. default: "https://registry.npmjs.org/" |
npm.tokenRef | string | Environment variable name that holds the registry auth token. default: "NPM_TOKEN" |
npm.packageManager | string | The package manager used to invoke the npm publish command. default: "npm"one of: "npm", "pnpm", "yarn", "bun" |
npm.tag | string | The dist-tag to publish under (e.g. latest, next, beta). default: "latest" |
npm.access | string | Package access level on npm. default: "public"one of: "public", "restricted" |
npm.provenance | boolean | Whether to publish with npm provenance (requires CI environment). default: false |
jsr | object | jsr publish configuration default: {"publish": false, "tokenRef": "JSR_TOKEN"… |
jsr.publish | boolean | Whether to publish to JSR. default: false |
jsr.publishArgs | array<string> | Additional arguments to pass to the JSR publish command. |
jsr.tokenRef | string | Environment variable name that holds the registry auth token (e.g. "JSR_TOKEN"). default: "JSR_TOKEN" |
jsr.packageManager | string | The package manager used to invoke the JSR publish command. default: "npx"one of: "deno", "npx" |
changelog | object | Changelog configuration default: {"enabled": true, "file": "CHANGELOG.md", "title"… |
changelog.enabled | boolean | Whether to generate/update the changelog. default: true |
changelog.file | string | Path to the changelog file. default: "CHANGELOG.md" |
changelog.title | string | Template for release title. default: "{{REVOLA_VERSION}} ({{REVOLA_DATE}})" |
changelog.includeTypes | array<string> | 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. default: ["BREAKING CHANGE", "feat", "fix", "perf", "refactor"… |
hooks | object | Shell commands to run at various lifecycle stages. Each key is a lifecycle hook name and the value is the command(s) to run. |
plugins | object | Defines plugins where each key is a plugin name and the value is its configuration object. |
Audit
What we found in this schema
- Declared draft: draft-07
- Validates cleanly against its own meta-schema.
- 42 properties, 98% carrying a description, max nesting depth 7.
Standards
Specification sections for the keywords in this schema
| Keyword | Document | Section |
|---|---|---|
$id | JSON Schema Core, draft 2020-12 | §8.2.1 — The "$id" Keyword |
$schema | JSON Schema Core, draft 2020-12 | §8.1.1 — "$schema" |
additionalProperties | JSON Schema Core, draft 2020-12 | §10.3.2.3 — "additionalProperties" |
anyOf | JSON Schema Core, draft 2020-12 | §10.2.1.2 — "anyOf" |
default | JSON Schema Validation, draft 2020-12 | §9.2 — "default" |
description | JSON Schema Validation, draft 2020-12 | §9.1 — "title" and "description" |
enum | JSON Schema Validation, draft 2020-12 | §6.1.2 — "enum" |
format | JSON Schema Validation, draft 2020-12 | §7 — Vocabularies for Semantic Content With "format" |
items | JSON Schema Core, draft 2020-12 | §10.3.1.2 — "items" |
minLength | JSON Schema Validation, draft 2020-12 | §6.3.2 — "minLength" |
pattern | JSON Schema Validation, draft 2020-12 | §6.3.3 — "pattern" |
properties | JSON Schema Core, draft 2020-12 | §10.3.2.1 — "properties" |
propertyNames | JSON Schema Core, draft 2020-12 | §10.3.2.4 — "propertyNames" |
type | JSON Schema Validation, draft 2020-12 | §6.1.1 — "type" |
uniqueItems | JSON Schema Validation, draft 2020-12 | §6.4.3 — "uniqueItems" |
format: "uri" | RFC 3986 (STD 66) | §3 — Syntax Components |
Documents
- JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
- JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
- RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.
Source
Attribution
This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.