Repository navigation
fix(ci): restore reader focus and security checks - #597
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.
Fix the reader keyboard regression behind CI run 36315630210. Enter previously required the selected article body to have loaded, so pressing it after navigation could leave focus on the list permanently. Focus now follows the selected article ID, including while its real response is pending.
The normal push security gate also detected newly published GHSA-3wwx-pv8p-q78v in Miniflare鈥檚 pinned Undici 7.29.0. The existing root override policy now selects patched 7.29.1; frozen installation and OSV pass without exceptions or registry changes. Both atomic repair commits are retained.
The existing browser journey now holds an actual article response and asserts focus both before and after it arrives. The original guard fails this regression; the correction passes. All existing assertions, isolation controls and workflow gates are preserved.
Validation: managed Chromium L3 28/28 with retries disabled; normal commit hooks passed lint, types, 912 unit tests and every coverage metric above 95%; actionlint and diff checks passed. Normal push hooks run real-HTTP L2, route coverage and required security scans. Validation was repeated with the patched HTTP dependency.