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/react@36.15.0

Minor Changes

• #4506d1419184511be5a3418fca437c805293456f0845 Thanks @owenniblock! - Export ActionBar default as ActionBar so it can be imported correctly

• #4423ee4608833ae79a9c05cbaa76f3602e40c9ba8554 Thanks @langermank! - Add support for the experimental Stack component

• #427613971c92669013ce6f5afe51782d251a5e2c5a17 Thanks @joshblack! - Add support for an experimental FeatureFlags component for working with feature flags in Primer

Patch Changes

• #45018bfab0a2760eb0734aea19b38ba5957a5deb8ca2 Thanks @pksjce! - ActionBar: Make it such that either aria-label or aria-labelledby is present

• #433177846c4e93cb0b7711654272162fa6f73d9cc90e Thanks @langermank! - Bug fix: Add word-break to ActionList items

[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 (integration pull request) : integration PR
  • 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]

size-limit report 📦

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