Repository navigation
fix(postgres): preserve Jotwink isolation and verify encrypted restores - #6
Merged
Merged
Conversation
kaanyagci
added this pull request to stack #56
October 8, 2026 06:39
kaanyagci
changed the title
kaanyagci
marked this pull request as ready for review
October 13, 2026 21:08
kaanyagci
force-pushed
the
codex/jotwink-databases
branch
from
October 13, 2026 21:28
9ed02b9 to
65bda94
Compare
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
1 participant
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.
Changes
Native GitHub stack
Native stack #56; prerequisite for #7.
Validation
Real disposable PostgreSQL TLS connections, CMS-encrypted backup and restoration of both databases passed. Nonempty target and TLS downgrade rejection, HBA safety, encryption and configuration checks passed. Existing unverified historical signatures were re-signed with identical file trees; remote checks rerun on the new SHA.
Release status
Reviewed and repaired as part of the shared-service PR sweep. This PR remains unmerged pending GitHub repository gates. No branch-protection bypass or production deployment is included in this review.