Versions

The release these pages describe

These pages describe LibreYOLO 1.5.0. The version sits at the top of the docs sidebar, and every page ends with a line naming the release it was verified against.

These URLs carry no version number and do not move. /docs/models/rf-detr is the current release's page for that family, today and after the next release. Pages are revised in place when behavior changes, so the verified-against line at the foot of a page is what tells you how current the text is.

Check what you have installed

libreyolo version prints the version together with the Python, torch and CUDA versions it is running against, which is usually what you want when something behaves differently from the docs. libreyolo --version prints the bare number and exits.

libreyolo version

import libreyolo print(libreyolo.__version__)

Documentation for earlier releases

Each earlier release keeps the single-page documentation it shipped with, at its own path.

Those pages are a record of what the library did at that release. They are not revised, so an argument that has since been renamed or a default that has since moved is still described there the old way. If you are pinned to one of those versions, its page is the accurate reference and this tree is not.

Pinning a release

pip install libreyolo installs the latest release published to PyPI. Pin the version when a result has to be reproducible:

pip install "libreyolo==1.4.0"

Installing from source, a plain clone checks out release, the stable branch whose code matches the published release. The dev branch carries work that has not been released yet, including anything listed under changelog as landing since the last version.

git clone https://github.com/LibreYOLO/libreyolo.gitcd libreyolopip install -e .

What changes between releases

Checkpoints move forward, not backward. A checkpoint written by a newer release can fail to load in an older one: the 1.4.0 notes record that checkpoints using the task strings introduced in that release, or carrying finalized quantization state, are not loadable by 1.3.1. Keep the version that wrote a checkpoint alongside the checkpoint itself.

Defaults move too, and the changelog records each one with its reason. In 1.4.0 PicoDet's lr0 went from 0.1 to 0.01, because the old default destroyed COCO-pretrained weights, and DEIM's went from 4e-4 to 1e-4. A training script that leaned on a default therefore reproduces differently across versions. Pass the values you care about explicitly and a run stays comparable.

Changelog summarizes what landed in recent releases, and CHANGELOG.md in the repository carries the full entries.