Move to soliplex 0.87¶
Part of Upgrading an existing stack.
Walk this rung with the v0.19b2 skill release — its generator
produces the rung's end state (soliplex 0.87.0 on the release images, with
haiku.rag 0.101.0). The
stack being upgraded names the release that generated it in its own
[tool.soliplex-template] manifest — use that one when climbing from an
older shape.
-
Stop the stack with
docker compose down, and back up the Postgres databases andrag/db/before upgrading. -
This rung is a pure release bump: the upgrade changes no template files beyond version spellings, sets up no database migrations (the last alembic migrations shipped with soliplex v0.86), and leaves the haiku.rag pair and docling-serve untouched. Stacks that changed the generated files by hand should compare the rung's cut with the one their manifest names to confirm nothing else moved.
-
Bump the baked soliplex image tags from
0.86.1to0.87.0: theFROMlines inbackend/Dockerfile(ghcr.io/soliplex/soliplex-postgres) and, if the stack ships the TUI,tui/Dockerfile(ghcr.io/soliplex/soliplex-tui). IfAGENTS.mdordocs/architecture/backend.mdname the release version, update those spellings to match. -
Update
soliplex_image_tagandsoliplex_dev_constraintin the project's manifest. Use>= 0.87.0, < 0.88for the Soliplex requirement in the root and packagepyproject.tomlfiles, then runuv lockin each project. -
Rebuild
backend,soliplex-dev, and the optionaltuiwithdocker compose build --pull. -
The default generated stack sets no migration policy, so the backend migrates its Alembic databases itself on startup. Stacks which configured a migration policy are responsible for driving their own migrations; the migrations reference describes running them with the CLI.
-
Start the stack with
docker compose up -dand inspect the backend logs. Then Check it, and commit.