Repository navigation
fix: reject stale upstream documentation publications - #12
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 33 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
7 tasks done
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.
Change
Reject a documentation check when the valid upstream publication generation is numerically older than the valid deployed generation. This stops the observed CDN propagation race before build/deploy. Document retry behavior.
Real production evidence
During #9 verification, run 39730808922 imported generation 39729808961-1 correctly. An immediate subsequent check, run 39731107060, received cached upstream generation 39728951124-1 while the deployed mirror was newer and imported the older output. The actual HTTP fixture now reproduces this ordering and rejects it.
Verification
Contributes to #9; after merge, verify the push restores the newest publication and the live endpoints agree.