Release tracking (37.2.0)

[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

• #5168 b9749d4 Thanks @TylerJDev! - TreeView: Adds indication of no nodes in a tree item, allows for `aria-expanded even if the item is empty.

• #5202 293c574 Thanks @hussam-i-am! - Update SubNav component to use CSS modules behind the feature flag primer_react_css_modules_team

Patch Changes

• #5225 e732591 Thanks @jonrohan! - chore(Banner): Move Banner CSS module flag from staff to ga

• #5177 26b54d8 Thanks @lukasoppermann! - Allow primitives dep to be if version 9 OR 10

[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
• Works in CodeSandbox or StackBlitz
  • New components render successfully
  • (optional) Tested in both SPA and SSR apps if release contains build changes

🌏 Integration tests

• Successful integration test with github/github 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 the review-lab
  • Manually test release-specific bugfixes and/or features work as described in the review-lab

🤔 Sanity test

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

🚢 After merge

• Upgrade @primer/react version at github/github

• Add the preview deployment's link to releases as a way of permalinking to old version's docs. Example

Please also leave any testing notes on the weekly release tracking issue. In particular, describing any issues encountered during your testing. This is helpful in providing historical context to the next release conductor as well as maintainers.

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	98.48 KB (0%)
packages/react/dist/browser.umd.js	98.91 KB (0%)

[siddharthkp]

Integration tests are passing 🎉