Repository navigation
Close publication connections before frontend builds - #79
Merged
Merged
Conversation
RaviTejaKNTS
temporarily deployed
to
production
October 21, 2026 12:04 — with
GitHub Actions
Inactive
This branch was previously deployed
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.
Page publication could crash after its database commit when a checked-out PostgreSQL connection dropped during the frontend build. The job now closes the snapshot connection before building and uses fresh connections for completion and failure recording.
Client and pool error events enter the normal failure path. The client listener is attached inside the checkout callback, before the promise resolves. Failed connections are discarded, and a failed retry or rollback cannot hide the original error. Current-release checks, public verification, and version-specific queue acknowledgement remain in place.
Validation:
npm run qualitypassed TypeScript and 116 core tests.git diff --checkpassed.After deployment, run the reviewed 67-page batch through the fixed publisher against the exact live main revision and confirm its public checks finish successfully.