Release tracking

[primer]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@primer/[email protected]

Minor Changes

• #7293 d418509 Thanks @lindseywild! - Adds character counts to TextInput and TextArea components

Patch Changes

• #7354 efbebdf Thanks @llastflowers! - update SelectPanel Multi Select Modal story

• #7426 094be60 Thanks @kelsey-myers! - Add focusPrependedElements prop to useFocusZone, FilteredActionList, and SelectPanel

• #7349 713d5a5 Thanks @mattcosta7! - PageLayout: Optimize drag/resize performance with inline styles and new optimizations

  Refactored:

  • Use direct attribute selectors (.Pane[data-dragging='true']) instead of descendant selectors for CSS containment (O(1) vs O(n) selector matching)
  • Extract optimization utilities to paneUtils.ts
  • Apply drag handle visual feedback via inline styles and CSS variables

  Added:

  • content-visibility: auto during drag/resize to skip off-screen content rendering
  • rAF throttle for drag updates (one update per frame, latest position wins)
  • Containment during window resize (parity with drag)

  These changes improve style recalculation performance on large DOMs (100k+ nodes) by eliminating descendant selector traversal.

• #7337 de970d6 Thanks @mattcosta7! - perf(Autocomplete): Split context to reduce unnecessary re-renders

  Split AutocompleteContext into separate contexts for static values, setters, and dynamic state.
  Components now subscribe only to the context slices they need, reducing re-renders.

• #7325 cc7e10e Thanks @mattcosta7! - perf(BaseStyles): Remove expensive :has([data-color-mode]) selectors

  Remove :has([data-color-mode]) selectors that scanned the entire DOM on every style recalculation.
  Input color-scheme is already handled by global selectors in the codebase.

• #7329 501a41f Thanks @mattcosta7! - perf(Dialog): Add feature flag for CSS :has() selector performance optimization

  • Add primer_react_css_has_selector_perf feature flag (default: false)
  • When flag is OFF: uses legacy body:has(.Dialog.DisableScroll) selector
  • When flag is ON: uses optimized direct body[data-dialog-scroll-disabled] data attribute with ref counting
  • Enables gradual rollout and easy rollback of performance optimization

• #7342 a8b42b2 Thanks @mattcosta7! - perf(hasInteractiveNodes): Optimize with combined selector and early attribute checks

  • Use combined querySelectorAll selector instead of recursive traversal
  • Check attribute-based states (disabled, hidden, inert) before getComputedStyle
  • Only call getComputedStyle when CSS-based visibility check is needed

[github-actions]

❗ Pre-merge checklist

Please ensure these items are checked before merging:

🔎 Smoke test

• All CI checks pass on this pull request
• Docs and Storybook open in a browser

🌏 Integration tests

• Successful integration test with github/github-ui as a primary consumer of primer/react (automated pull request)
  • Verify all CI checks have passed on automated pull request
  • Manually test critical paths in preview
  • Manually test release-specific bugfixes and/or feature work as described in preview

✅ Peer Review

• Create release review issue for Issues team (example)
• Wait for approval from Issues team before merging

🤔 Sanity test

• All bugfixes in this release have resolved their corresponding issues
• The issues for any reverted PRs have been re-opened and commented on with a link to the reverted PR
• No noticeable regressions have been introduced as a result of changes in this release
• Release notes accurately describe the changes made

❗ Post-merge checklist

Please ensure these items are checked after merging:

🚢 Version upgrade, cleanup, and documentation

• Upgrade @primer/react version at github/github-ui
• Close Integration test PR and delete branch
• Leave a /short-report comment on quarterly release conductor tracking issue summarizing time spent on release activities and any challenges encountered
• Leave any testing notes on the automated per-shift release tracking issue. In particular, describe any issues encountered during your testing. This is helpful in providing historical context to the next release conductor as well as other maintainers.

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Or, apply the integration-tests: skipped manually label to skip these checks.

[primer-integration]

👋 Hi from github/github-ui! Your integration PR is ready: https://github.com/github/github-ui/pull/9989

[primer-integration]

🔬 github-ui Integration Test Results

Check	Status	Details
CI	✅ Passed	View run
Projects (Memex)	✅ Passed	View run
VRT	✅ Passed	View run

✨ All checks passed! Your integration PR is ready for review.

[TylerJDev]

https://github.com/github/github-ui/pull/9989 is green! adding the label as github-ui/vrt step seems to be stuck