chore(release): v4.3.0 #533
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/release-v4.3.0"
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?
Cuts v4.3.0, Product Surface: Navigation, Attention & Feedback. All 34 issues of the milestone are merged (build order and per-phase record on #514):
APP_VERSIONandBOT_EXPECTED_APP_VERSION→ 4.3.0;make check-versionspasses;alembic headsis one head. Three additive migrations (f0ab1c2d3e4f → fa0b1c2d3e4f → 0b1c2d3e4f5a), bot contract v1 unchanged (every/api/bot/*addition is additive), one new public route (GET /api/invites/{code}), a relaxed CSP for the backend's two HTML pages only, no new settings. The changelog section carries the operator preamble;[Unreleased]is empty.After merge: tag
v4.3.0, deploy dev → validate → deploy prod (three migrations apply) → validate (bot handshake on 4.3.0,/helpregistered) → close #514.🤖 Generated with Claude Code
Deployed.
docker-test)docker-host-mcp)9dd77989dd7798, from v4.2.30b1c2d3e4f5a (head), no upgrades (already there from the per-phase deploys)0b1c2d3e4f5a (head)aftere9fa0b1c2d3e → f0ab1c2d3e4f → fa0b1c2d3e4f → 0b1c2d3e4f5a, migrate exit 0/ready200,/help/gm200, unknown invite code 404, old recording address serves the redirect pageVersion handshake OK: backend 4.3.0, bot API contract v1; commands synced; no message-content intent warning any moreProd went straight from v4.2.3; dev had been deployed after each phase, so its schema was already at the head.