0.1.0

First release of disttown, the CLI for publishing releases on your own terms: records in your repo, artifacts on storage you control, everything content-addressed.

Publishing

• disttown publish hashes artifacts locally and lands the project record, release, and pointer moves in one atomic commit — a release either fully exists or doesn't.
• --blobs stores artifact bytes on your own PDS; the default targets any dumb HTTPS bucket you control.
• Version strings are opaque and claimed earliest-live-wins: semver, ChronVer, whatever your project speaks.

Storage

• disttown storage setup and storage doctor check the things that actually break: anonymous GET, ETag and Content-Length behavior, and a permanent canary round-trip.

Lifecycle

• disttown pointer set moves channels (latest, next, …) atomically.
• disttown yank writes a status record and repoints in the same commit — downloads by explicit version keep working, channel resolution refuses.

Trust

• Releases resolve without dist.town in the loop: handle → PDS → records → digest-verified bytes. The AppView is a convenience, never a dependency.
• Checksums come from the publisher-signed release record, so a compromised bucket cannot forge them.

Four platform artifacts ship with this release: linux/amd64, linux/arm64, darwin/amd64, and darwin/arm64 — each digest-pinned in the release record.