Schema change on 19.0 without module upgrade takes Cloudpepper prod down

[rutgerhofste]

On 2026-09-22 #246 (b3c5dc4) added pan_mail_license.setup_reported. Cloudpepper pulled the code and restarted, but ran no -u pan_mail_pro (auto_upgrade is off on odoo.pantalytics.com). Every web client load then failed with UndefinedColumn via ir_http.session_info -> improve_config, and the fetch cron stopped. GET /odoo returned 500 from 13:09 to 13:18 UTC.

Fixed by hand with button_immediate_upgrade.

Pick one:

• turn on auto_upgrade for pan_mail_pro on our prod (and check it for customer instances on auto-pull), or
• make session_info never touch the license record (a crash there breaks the whole backend, not just Mail Pro).

🤖 Generated with Claude Code

[rutgerhofste]

Real cause: Cloudpepper's auto_upgrade was already on. It skips -u when the manifest version hasn't changed. Since #236 the version bump runs in release.yml after the merge, and 19.0's classic branch protection refuses that push ("Changes must be made through a pull request"). The last three release runs (#243, #244, #246) failed, and the version stayed at 19.0.20.2.0.

Fix (docs/release.md step 1): swap the classic protection for a ruleset with the same rules and GitHub Actions (integration 15368) as bypass actor, then re-run release run 35731540148 so it bumps to 19.0.20.3.0 and tags it.

[rutgerhofste]

Change of plan: no bypass. #249 reverts #236 (the PR bumps its own version again) and compares with 19.0's tip. Branch protection comes back with "require branches to be up to date".

[rutgerhofste]

#256 (gemerged 29-09) vangt het session_info-pad af: ontbrekende tabel/kolom geeft geen 500 meer, Mail Pro meldt zich als niet verbonden tot -u draait. Rest (nieuw stored veld op res.users) staat in #255.