The image's Node 22 and Python 3.12 base images are a major version behind #159

Closed
opened 2026-10-08 23:17:22 -04:00 by cmoriarty · 1 comment
Owner

#155 moved the pins inside the image and left its base images alone: node:22-bookworm-slim and python:3.12-slim-bookworm. Both have newer major lines.

What it needs

  • Decide the Node line runs get (a run's own npm and npx playwright test use it), and move NODE_IMAGE, the node 22 check in deploy/docker/selfcheck.sh, the deployment spec's mention of Node 22, and @types/node together.
  • Decide whether osfd moves to a newer Python; requires-python = ">=3.12" already allows it, and the lanes already run on 3.13 locally.
  • Rebuild, and run the self-check and the simulated runs in the image.

Done when

The image runs on the chosen versions, braid-selfcheck passes, and the deployment spec names them.

#155 moved the pins inside the image and left its base images alone: `node:22-bookworm-slim` and `python:3.12-slim-bookworm`. Both have newer major lines. ## What it needs - Decide the Node line runs get (a run's own `npm` and `npx playwright test` use it), and move `NODE_IMAGE`, the `node` 22 check in `deploy/docker/selfcheck.sh`, the deployment spec's mention of Node 22, and `@types/node` together. - Decide whether osfd moves to a newer Python; `requires-python = ">=3.12"` already allows it, and the lanes already run on 3.13 locally. - Rebuild, and run the self-check and the simulated runs in the image. ## Done when The image runs on the chosen versions, `braid-selfcheck` passes, and the deployment spec names them.
Author
Owner

Shipped as newer-image-runtimes.

  • The image runs Node 26 (node:26-trixie-slim) and Python 3.14 (python:3.14-slim-trixie), both on Debian 13. Node 26 becomes LTS on 2026-10-28; Node 24 moves to maintenance on 2026-10-20, and Python 3.13 is already security-only.
  • The runtime stage installs libatomic1, which Node 26's binary links and the Python image lacks.
  • A new braid-check-runtimes, called by braid-selfcheck, checks both versions. A unit test holds the Dockerfile, the self-check and ui @types/node (now 26) to the same lines. The global npm install passes --allow-scripts=opencode-ai, which npm 11.20 asks for.
  • The deployment spec, the docs and openspec/config.yaml name the new versions.

Verified. The fast and full lanes passed on the integrated batch (3,388 backend tests, 681 vitest, 249 browser specs with the slow and live ones, 29 of 29 simulated runs), and it is live on production as 57971c2 (deploy run 138, self-check braid-selfcheck: ok). Archived in a6ae0dc. The deploy's self-check printed ok node 26.12.0 and ok python 3.14.8; in the production container, a run's shell finds the same. The unit suite also passed on Python 3.14 in an environment of its own.

Not done: the laptop's own lanes keep the Python their .venv was built with (3.13 here). Pinning them to 3.14 would rebuild every worktree's .venv while other sessions use them.

Shipped as `newer-image-runtimes`. - The image runs **Node 26** (`node:26-trixie-slim`) and **Python 3.14** (`python:3.14-slim-trixie`), both on Debian 13. Node 26 becomes LTS on 2026-10-28; Node 24 moves to maintenance on 2026-10-20, and Python 3.13 is already security-only. - The runtime stage installs `libatomic1`, which Node 26's binary links and the Python image lacks. - A new `braid-check-runtimes`, called by `braid-selfcheck`, checks both versions. A unit test holds the Dockerfile, the self-check and `ui` `@types/node` (now 26) to the same lines. The global npm install passes `--allow-scripts=opencode-ai`, which npm 11.20 asks for. - The deployment spec, the docs and `openspec/config.yaml` name the new versions. **Verified.** The fast and full lanes passed on the integrated batch (3,388 backend tests, 681 vitest, 249 browser specs with the slow and live ones, 29 of 29 simulated runs), and it is live on production as 57971c2 (deploy run 138, self-check `braid-selfcheck: ok`). Archived in a6ae0dc. The deploy's self-check printed `ok node 26.12.0` and `ok python 3.14.8`; in the production container, a run's shell finds the same. The unit suite also passed on Python 3.14 in an environment of its own. Not done: the laptop's own lanes keep the Python their `.venv` was built with (3.13 here). Pinning them to 3.14 would rebuild every worktree's `.venv` while other sessions use them.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#159
No description provided.