Merged
Conversation
Contributor
Author
|
🤖 Screenshot check with deterministic mocked API data. The mock makes the latest Ferry run and latest Build commit amber, so the ordering is visible at a glance. Before ( After (this PR): latest amber square is on the right. Capture setup: local Vite dashboard, |
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
Render the infra status page history strips oldest-to-newest so the most recent GitHub Build and Ferry status squares appear on the right.
Root Cause
The GitHub APIs return workflow runs and commit history newest-first. The dashboard used those arrays directly for the compact status strips, so time flowed right-to-left even though the latest-line logic correctly treated index 0 as newest.
Changes
commits[0]as the latest commit.Validation
npm run lintnpm run typechecknpm run build