Vancetope 0.4.1 is out

Vancetope 0.4.1 is tagged and pushed — a patch release with a single change, and that change is about who decides when your software changes.

Pinned by default

Until now, a stack from the setup wizard pulled the latest images. A docker compose pull on a Tuesday could mean a different Vancetope on Wednesday — new behavior, nothing you asked for, and no easy way back.

As of 0.4.1 the wizard writes the version of the image it runs from into IMAGE_TAG in .env. A stack built by the 0.4.1 wizard stays on 0.4.1, no matter what latest does overnight. Stacks from earlier releases pick the pin up the next time you re-run the wizard.

Updating is one command — an explicit one

Upgrading on purpose means re-running the wizard from the new image. It bumps the pin and re-renders the compose files with the current template:

cd ~/.vancetope
docker run --rm -it -v "$PWD:/data" \
  mhus/vancetope-anus:<new version> --setup-docker-compose
docker compose pull && docker compose up -d

Data is migrated automatically when the new brain boots.

Prefer the old behavior? Pick latest for the image tag in the wizard’s expert mode — the pin never changes, and docker compose pull && docker compose up -d alone is the whole update. The rolling channel is still there; it’s just not the default anymore.

The getting-started guide documents both paths.