Repository navigation
Diagnose dev program differences against pre-upgrade backup - #852
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.
The post-upgrade DEV fingerprint check detected one changed PartnerProgram and no missing records. Compare the protected pre-deployment archive with the live program rows using typed PostgreSQL values in a read-only transaction. Logs contain only program IDs and changed field names. A hash mismatch is cleared only when every archived program field matches and archive primary keys match the original manifest.
Run the independent CDN and single authorized control-email acceptance before reporting an unresolved data mismatch. Unexpected changes still fail verification. Existing email receipts prevent automatic duplicate delivery. This changes only the DEV verification helper and does not redeploy the application.
Validation: six disposable PostgreSQL 16 checks (real COPY Unicode/NULL/JSON/timestamps, changed-field and deletion detection, enforced read-only mode, malformed archive rejection); 11 existing backup and email-receipt checks; Black, Flake8 and git diff --check passed.