Version and Release Channels
The authoritative source version is package.json; an installed binary reports it with vibepro version.
| Channel | Expected after this release | Authority |
|---|---|---|
npm latest | 0.2.0-beta.12 | Live npm registry dist-tag |
npm beta | 0.2.0-beta.12 | Live npm registry dist-tag |
Repository main | 0.2.0-beta.12 release source | Git commit and package.json |
| Manual build | Source commit in footer/meta | Deployed VitePress artifact |
The table identifies the current release channels. The sections below are an append-only ledger of published versions; detailed PR evidence remains in Release Notes.
0.2.0-beta.12
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.11
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.10
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.9
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.8
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.7
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.6
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.5
Detailed changes for this published version are recorded in Release Notes.
0.2.0-beta.4
Separates evidence that a problem exists from evidence for its solution direction in the Senior Engineering Judgment DAG. Structural excess routes to SIMPLIFY, value constraints to VALUE, and insufficient or unknown decision evidence to VALIDATE. This breaking beta updates the senior judgment input schema from 0.2.0 to 0.3.0.
0.2.0-beta.3
Publishes the rebuilt minimal core and aligns the npm README, VitePress entry pages, generated CLI reference, and CI with that contract. This is a breaking beta change: commands and automatic control-plane mechanisms removed by the rebuild are not compatibility aliases.
0.2.0-beta.2
The previous published beta contained the broader evidence-gate and managed workflow. Pin this version only when migration time is required; it does not represent the current minimal-core direction.
The installed binary's help output wins if documentation and a locally installed version differ.
See Release Notes for the chronological publication and development record.