chant.config.ts:149 and src/params.ts:20 both default image to ghcr.io/binarybourbon/fountain:v0.7.0. Fountain is at v0.16.0.
What that costs on a laptop today: v0.7.0 predates the team roster, teammate schedules, webhook endpoints, the sandboxes routes and the acp flag on a conversation. just up therefore produces an instance whose API is missing most of what its own docs describe, and a client generated from the current OpenAPI spec fails against it in ways that look like client bugs.
Found while verifying a client against a laptop instance: just up came up on v0.7.0, and every team-side call 404ed until I redeployed with
just params="--param image=ghcr.io/binarybourbon/fountain:v0.16.0" up
after which all of it worked, including the roster, the schedules and the SSE stream.
Two things worth deciding together:
- Move the default to the current release. A pin is right; this one has just gone stale.
- Say how it gets refreshed, since the same drift will recur. Either a note in the release checklist, or a small job that opens a PR when a newer tag exists.
src/app/deployment.ts:14 already carries a version-conditional comment, so the file knows about version skew; the default is the part nothing watches.
The docs' five-minute laptop path is the first thing anyone runs, and right now it hands them a build from nine releases ago without saying so.
chant.config.ts:149andsrc/params.ts:20both defaultimagetoghcr.io/binarybourbon/fountain:v0.7.0. Fountain is at v0.16.0.What that costs on a laptop today: v0.7.0 predates the team roster, teammate schedules, webhook endpoints, the sandboxes routes and the
acpflag on a conversation.just uptherefore produces an instance whose API is missing most of what its own docs describe, and a client generated from the current OpenAPI spec fails against it in ways that look like client bugs.Found while verifying a client against a laptop instance:
just upcame up on v0.7.0, and every team-side call 404ed until I redeployed withafter which all of it worked, including the roster, the schedules and the SSE stream.
Two things worth deciding together:
src/app/deployment.ts:14already carries a version-conditional comment, so the file knows about version skew; the default is the part nothing watches.The docs' five-minute laptop path is the first thing anyone runs, and right now it hands them a build from nine releases ago without saying so.