Repository navigation
Retire the expected upgrade changes v0.3.0 contains - #340
Merged
Merged
Conversation
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 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last step of cutting v0.3.0 (
docs/releasing.md, step 7).v0.3.0 contains migration
20261109100003(spec 049 drops the sessions'ip_addressanduser_agent). From now on the upgrade proof upgrades from v0.3.0, so it never sees that change, and its two entries come out ofscript/upgrade/expected_changes.yml, which is nowchanges: [].Verification
bin/rspec spec/script/upgrade: 136 examples, 0 failuresbin/cipassed on 017e080🤖 Generated with Claude Code