Repository navigation
fix: keep patch release details inline with each fix - #275
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.
What Problem This Solves
Patch release notes repeat a full-width details row after every fix, making the list harder to scan.
User Impact
An opt-in native “More details” control follows the fix sentence instead, while PR links and thanks remain expandable and keyboard-accessible.
Why This Change Was Made
Add a scoped inline layout for the existing release-source disclosure. Keep its native toggle, focus indicator and 44px touch target; ordinary disclosures are unchanged. No parser or JavaScript changes.
This is the renderer dependency for the 10.4 notes draft. Neither PR is authorized for merge or live publication by this presentation request.
Evidence
35f1facdccfand renderer263e8efecd7; desktop inline-flow, keyboard and no-overflow checks passed. Earlier proof is retained.Before
After