chore: pin Review Loop Action with bounded dispatch recovery - #1743
Merged
Conversation
Signed-off-by: Jake Gaylor <jhgaylor@gmail.com>
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.
Pin Review Loop Action v1.0.1 so brief service outages and lost acknowledgments retry with the same admission identity. The release adds bounded backoff, honors Retry-After, and leaves authentication refusals and invalid results as failures.
Release: https://github.com/managoat/review-loop-action/releases/tag/v1.0.1
Validation: Fountain precommit passed 4,587 tests and six doctests, with two skips and seven exclusions. The public Action passed 13 Node tests and its public-consumer smoke check.
Draft while the designated #1665 acceptance run uses the current approved base. Merge after that run ends so its policy revision is not replaced mid-test. This workflow change becomes authorized only after it reaches the trusted base.