Release v0.19.0#38
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.
Release v0.19.0
Cuts a new minor release with all fixes and features merged to
mainsince v0.18.0 (PRs #27–#37). Adds the v0.19 section toCHANGELOG.md; no code changes.This is a minor bump (not a patch) because it adds a new CLI flag (
--defer-validate-fks) and changes default FK-creation behavior.Highlights
Foreign-key constraint handling (theme of the release)
--defer-validate-fks— create target FKs asNOT VALIDto skip the historical-row validation scan and let the COPY → CDC handoff happen immediately (Add --defer-validate-fks to create FK constraints as NOT VALID #37)NOT VALIDretry on pre-existing data violations (SQLSTATE 23503), instead of failing the migration (Handle FK constraints directly with automatic NOT VALID retry #27)CDC / follow robustness
--followtarget connection loss (Add retry with backoff to follow pipeline on target connection failure #35)jsoncolumns with REPLICA IDENTITY FULL (Handle REPLICA IDENTITY FULL for json columns #28)Data integrity / resume
--drop-if-existsresume assumption (Resume audit follow-ups: blobs flag + drop-if-exists comment #34)Security / CI
After merge
Tag from
mainto trigger the multi-arch Docker publish:Test plan
main(already CI-green from the individual PR merges)