Skip to content

fix: keep patch release details inline with each fix - #275

Merged
hannesrudolph merged 1 commit into
mainfrom
fix/release-more-details-inline
Oct 16, 2026
Merged

hannesrudolph merged 1 commit into
mainfrom
fix/release-more-details-inline

Conversation

@hannesrudolph

@hannesrudolph hannesrudolph commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

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

  • Focused Chromium test passes at desktop and narrow widths, checking same-line placement, no horizontal overflow, click/Space/Enter toggling and Tab/Shift-Tab source-link access.
  • Independent review found no blockers. Existing prose, sections, links, credits and release facts are unchanged.
  • The rebuilt native Studio preview uses release source 35f1facdccf and renderer 263e8efecd7; desktop inline-flow, keyboard and no-overflow checks passed. Earlier proof is retained.

Before

Previous patch view with a separate sources and thanks row

After

More details follows each fix sentence in the inline patch view

@hannesrudolph
hannesrudolph marked this pull request as ready for review October 16, 2026 02:59
@hannesrudolph
hannesrudolph requested a review from a team as a code owner October 16, 2026 02:59
@hannesrudolph
hannesrudolph merged commit ba8fd13 into main Oct 16, 2026
4 checks passed
@hannesrudolph
hannesrudolph deleted the fix/release-more-details-inline branch October 16, 2026 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant