chore(release): v4.5.0-rc1 #1048
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/release-4.5.0-rc1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The first prerelease, for testing the v4.5.0 redesign on the dev server (#1043; the owner approved the name and the dev cutover on 2026-10-03). It follows the new "Cutting a prerelease" procedure in
docs/OPERATIONS.md:APP_VERSION,BOT_EXPECTED_APP_VERSIONand the six image tags indocker-compose.images.ymlare set to4.5.0-rc1.changelog.d/for the final 4.5.0, andrelease.ymlrenders the prerelease's notes from them.v4.5.0-rc1. The images are published as:4.5.0-rc1only, never:latest, and dev is cut over to them.For whoever upgrades from 4.4.1:
BOT_CONTRACT_VERSIONis 2 (it was 1 at 4.4.1), so the bot and the backend must be upgraded together.Changelog
Test plan
check_version_sync.py:Version sync OK — app 4.5.0-rc1, bot contract v2.test_bot_meta,test_version_handshakeand the/api/metatest read the constants.🤖 Generated with Claude Code