Is it safe to update TubeArchivist?
Tracking tubearchivist/tubearchivist
Update with care.
Two behavioral changes warrant attention before upgrading: the stricter download error handling (bot errors now stop the entire task) may surface failures that previously passed silently, and the overhauled POT plugin installation method could affect existing setups that relied on the prior loading path. The automatic cleanup of deprecated appconfig keys is also a one-way migration step. No explicit breaking changes or manual migration steps are documented, but these behavioral shifts are worth reading before applying the update.
What changed
v0.5.10 adds the ability to load secrets from a file rather than environment variables, improving deployment security for sensitive configurations. The release also cleans up deprecated app-config keys automatically on startup. Several internal improvements ship alongside: the redownload workflow now uses reindex for better metadata preservation, the POT plugin installation method has been overhauled to fix runtime loading into yt-dlp, and download error handling is stricter — a bot error now halts the task entirely rather than continuing silently. Four bug fixes round out the release, including ES9 compatibility for newer Elasticsearch alias APIs and a fix for video deletion from playlists when out of sync.
Source
Every verdict on Bumplog traces back to a GitHub release. No invented details.
