kevinveenbirkenbachandClaude Opus 5.5 678011cca0 feat(web-app-peertube): run the release migration scripts and refresh the client on upgrade ...

PeerTube 8.0, 8.1 and 8.3 ship scripts that must run after the server
migrations, and the image-seeded peertube_assets volume keeps the old
client forever. Before the pinned image starts, the role reads the release
the data was written by from a marker file and application.migrationVersion
(table of every release's last migration from 6.0.0 to 8.3.1) and plans the
upgrade; a downgrade or data older than the table stops the deploy. After
the server is healthy it asserts the pinned migration version, runs every
dist/scripts/migrations/peertube-X.Y.js above the data's release in order,
empties /app/client/dist so Docker reseeds it from the pinned image, and
records the pinned release in the marker. The health wait allows 30
minutes while existing data migrates.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-22 10:18:09 +02:00

..

filter_plugins

feat(web-app-peertube): run the release migration scripts and refresh the client on upgrade

2026-10-22 10:18:09 +02:00

__init__.py

…