95f499bb2d
Some checks failed
CI / lint (push) Failing after 1m8s
CI / notebooks-smoke (push) Successful in 2m5s
Deploy / changes (push) Successful in 18s
Infra CI / notebooks (push) Failing after 49s
CI / test (push) Successful in 5m5s
Infra CI / zotero (push) Successful in 39s
Infra CI / api (push) Successful in 27s
Infra CI / docs (push) Successful in 36s
Infra CI / bcda (push) Successful in 25s
Infra CI / llm (push) Successful in 23s
Infra CI / mc (push) Successful in 40s
Deploy / zotero (push) Has been skipped
Deploy / docs (push) Has been skipped
Deploy / api (push) Has been skipped
Deploy / bcda (push) Has been skipped
Deploy / llm (push) Has been skipped
Deploy / mc (push) Has been skipped
Deploy / report (push) Has been cancelled
Deploy / notebooks (push) Has been cancelled
dev/scripts/marimo_latest.py, run by a nightly systemd user timer, moves
the notebooks image to the newest stable marimo release past the stack's
7-day cooldown: bump the Dockerfile pin, build, gate with nb_fe_smoke
--image (the overlay guards already fail the build if marimo's chrome
controls come back), commit just the pin on main and push, roll the
container and probe it live. A failure restores the pin (and HEAVY_TAG),
skips that release until a newer one, and files a Gitea issue. Renovate
was meant to bump this pin but has processed no repository in weeks
("No repositories found"), and nothing ever rolled its bumps anyway.
The image sets MARIMO_SKIP_UPDATE_CHECK=1, so marimo no longer polls
PyPI and the editor's "Update available" toast is gone.