RELEASES.md

# Canter releases

[Model card](README.md) · [Getting started](README.md#getting-started) ·
[API and inference parameters](API.md)

Checkpoint tags are immutable snapshots. The installed package supplies the
inference code, so current code can load any compatible checkpoint tag without
executing the Python files stored in that historical snapshot.
The current package also supplies the small latent-RGB preview projection;
preview behavior therefore follows the installed code rather than changing an
older denoiser checkpoint tag.

Canter `0.3.0` adds asynchronous native-resolution latent previews and the
responsive preview grid. The browser scales previews for display; final
decoded images remain full resolution.

| Release | Date | Weight storage | Status |
| --- | --- | --- | --- |
| [`v0001`](https://huggingface.co/data-archetype/canter/tree/v0001) | July 2026 | bfloat16 with float32 precision islands | Preview |

## Updating code

Refresh the moving `main` directory and use an editable installation:

```bash
hf download data-archetype/canter --revision main --local-dir canter
python -m pip install -e ./canter
```

For a Git clone on `main`, use `git pull`. If the checkout was installed
without `-e`, reinstall it after updating.

## Selecting a checkpoint

Remote API and web UI loading can select any compatible checkpoint explicitly:

```python
pipe = CanterPipeline.from_pretrained(
    "data-archetype/canter",
    revision="v0001",
)
```

```bash
canter-web --model data-archetype/canter --revision v0001 --in-browser
```

These commands use the currently installed code and download only the selected
checkpoint artifacts. Running `app.py` inside a tagged standalone directory
instead uses the historical code bundled with that snapshot.

For exact reproduction, pin both the Canter package version and checkpoint
tag. Passing `revision="main"` explicitly selects the moving repository head
and is not an immutable checkpoint reference.

## v0001

Initial preview release.