Repository navigation
Align generated robots with native release matrix order - #30
Merged
Merged
Conversation
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.
The protected Pages staging check on PR29 correctly stopped deployment because the builder reused the navigation array, which is sorted oldest-first, while the native validator expects release-matrix order. Use the unchanged native archiveReleases array instead. This is a one-line repair; crawler semantics, archive exclusions, all copy and every release gate remain unchanged. The original mismatch was reproduced locally. Exact production expression checks now pass both current v0.40 and a future-version fixture, with all archives excluded and current allowed. Full native CI and Pages gates remain required.