Versioning and changelog
Each published version of the API has a number, kept in VERSION at the root of the
voplica/api repository, and a tag v<number>. A new version is published only when
the published definitions or their documentation change, and its number is then higher than the last one. The client
packages carry the same number: @voplica/connect, com.voplica:voplica-api and voplica-api.
The numbers follow semantic versioning: a breaking change to the published definitions raises the major number, an addition raises the minor number, and a change to comments or documentation alone raises the patch number.
Below, newest first, is each version’s entry; the oldest is the initial public release. From the second version on,
each entry opens with buf’s breaking-change verdict against the version before, the evidence for its number, then
lists what was added, removed or changed (services, methods, messages, enums, fields, enum values), or says only the
documentation changed. Read an entry before you upgrade, and pin the version you tested.
1.0.1 (2026-10-26)
Section titled “1.0.1 (2026-10-26)”buf breaking against 1.0.0: none.
- Documentation only.
1.0.0 (2026-10-25)
Section titled “1.0.0 (2026-10-25)”The initial public release of the Voplica API: 211 RPCs in 20 services.