Release tracking

[primer[bot]]

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

• #7157 eddd934 Thanks @joshblack! - Add feature flag to control whether Spinner animations are synchronized

• #7277 4a1c9a5 Thanks @kendallgassner! - Added callback prop onActiveDescendantChanged to FilteredActionList

[github-actions[bot]]

❗ Pre-merge checklist

Please ensure these items are checked before merging:

🔎 Smoke test

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

🌏 Integration tests

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

✅ Peer Review

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

🤔 Sanity test

• [x] All bugfixes in this release have resolved their corresponding issues
• [x] The issues for any reverted PRs have been re-opened and commented on with a link to the reverted PR
• [x] No noticeable regressions have been introduced as a result of changes in this release
• [x] 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[bot]]

:wave: 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.

[llastflowers]

integration tests passing: https://github.com/github/github-ui/pull/8533