[patch] Limit retry hints to pre-dispatch failures#24
Merged
Conversation
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
libops-agent
marked this pull request as draft
July 13, 2026 20:02
Contributor
Author
|
The new PR preflight is intentionally blocking merge: WIF reaches the configured credential chain, but impersonation of the dedicated publisher still fails because the An authorized operator must apply the full |
libops-agent
force-pushed
the
retry-after-pre-dispatch-safety
branch
5 times, most recently
from
July 14, 2026 16:05
f23873b to
a7174a1
Compare
libops-agent
force-pushed
the
retry-after-pre-dispatch-safety
branch
from
July 14, 2026 19:14
a7174a1 to
9bcb12a
Compare
libops-agent
marked this pull request as ready for review
July 14, 2026 19:27
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.
Summary\n\n- classify exhausted pre-connect backend dials as safely retryable\n- emit Retry-After only when a request was not dispatched\n- omit retry hints after permanent power failures and ambiguous post-connect failures\n- prove POST bodies are delivered at most once across a post-connect reset\n- make the explicitly dispatched tagged GoReleaser workflow call and await the existing shared GHCR/GAR image workflow\n- keep human/PAT tag pushes on their existing direct image path without duplicate publication\n- keep PPB as a thin caller of the pinned libops/.github publisher; GHCR is universal and GAR is added because PPB runs on Cloud Run\n\n## Validation\n\n- go test -race ./...\n- gofmt -d\n- actionlint\n- git diff --check\n\n## Release gate\n\nDepends on libops/api#44. Merge that Terraform correction, run one full non-targeted iac/libops-images apply during a publication-free window, then dispatch this branch build workflow from a trusted ref and verify successful pushes to both GHCR and GAR. Only then make this PR ready and merge it. After merge, the 0.5.1 GoReleaser run must remain green through its nested publish-images job, and both registry tags must be verified before cloud-compose is updated.