From 017e0800c14a8d0abfab2f246b7a328cf2ebc6b9 Mon Sep 17 00:00:00 2001 From: James Thompson Date: Thu, 12 Nov 2026 11:52:42 -0500 Subject: [PATCH] chore(upgrade): retire the expected changes v0.3.0 contains v0.3.0 holds migration 20261109100003 (spec 049's dropped session columns), so the proof from v0.3.0 on never sees that change; its two entries go (docs/releasing.md step 7). Co-Authored-By: Claude Opus 5.5 --- script/upgrade/expected_changes.yml | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/script/upgrade/expected_changes.yml b/script/upgrade/expected_changes.yml index c3f22306..e3c666a3 100644 --- a/script/upgrade/expected_changes.yml +++ b/script/upgrade/expected_changes.yml @@ -2,14 +2,4 @@ # docs/specs/031-upgrade-from-previous-release/contracts/yaml-files.md. A difference between the old and the upgraded # database that is not listed here fails the upgrade proof. After tagging a release, delete the entries whose migration # it contains (docs/releasing.md). -changes: - - table: sessions - column: ip_address - kind: dropped - migration: "20261109100003" - reason: "Spec 049 decision 5: a session no longer stores the client's address" - - table: sessions - column: user_agent - kind: dropped - migration: "20261109100003" - reason: "Spec 049 decision 5: a session no longer stores the client's user agent" +changes: []