Product guide

Every release, explained.

Product changes should be understandable at the point of upgrade. Juror releases are tied to source history rather than a generic marketing timeline.

Direct answer

Product changes should be understandable at the point of upgrade. Juror releases are tied to source history rather than a generic marketing timeline.

01Release provenance
02Migration notes
03GitHub release links

How it works

Product changes should be understandable at the point of upgrade. Juror releases are tied to source history rather than a generic marketing timeline.

For every release, explained., use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.

Limits to keep in view

Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.