Repository navigation
Isolate historical migration fixtures - #566
Merged
Merged
Conversation
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.
Historical migration tests now construct their records at the schema versions they exercise. They no longer downgrade current retained allocations through the cutover migration, whose data-preservation guard correctly refuses that operation.
Preserves the existing ciphertext, endpoint, retained-generation and allocation-history assertions. Production migrations and rollback guards are unchanged. Validation: the historical migration/downgrade family and the affected CI integration shards pass against PostgreSQL; focused vet and repository hygiene pass.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.