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]

Patch Changes

• #7334 ea4789f Thanks @mattcosta7! - perf(TreeView): Cache tree items in typeahead for better INP

  • Add useTreeItemCache hook to cache DOM queries for tree items
  • Update useRovingTabIndex and useTypeahead to use cached items
  • Add documentation for acceptable :has() selector usage

• #7347 72c7a7f Thanks @owenniblock! - Only shows the aria-describedby id for loading when the component is in the loading state

[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.