# Canter releases

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

The default package behavior is pinned to the release shown in the model card.
It does not automatically follow the repository's `main` revision.

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

## Updating

Download a new release into a new directory and reinstall it:

```bash
hf download data-archetype/canter --revision v0002 --local-dir canter-v0002
cd canter-v0002
python -m pip install --upgrade .
```

Remote API and web UI loading can select the new release explicitly:

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

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

Passing `revision="main"` explicitly follows the moving repository head.
Pinned release tags are recommended for normal use.

## v0001

Initial preview release.