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@38.4.0

Minor Changes

• #7258 8e66a2c Thanks @kendallgassner! - Make MappedActionListItem a forwardRef component

• #7250 a193d30 Thanks @siddharthkp! - Banner: Add flush prop for use within confined spaces, such as dialogs, tables, cards, or boxes where available space is limited.

• #7247 e1021e7 Thanks @liuliu-dev! - Add leadingVisual to InlineMessage component.

• #7047 c07dd71 Thanks @TylerJDev! - Remove the feature flag for primer_react_segmented_control_tooltip and GA tooltip by default behavior.

  • Ensure that when disabled is applied, the tooltip is still triggered.

Patch Changes

• #7244 d973c5a Thanks @lukasoppermann! - "Update logic for how hex codes are applied"

• #7230 534ca11 Thanks @mperrotti! - Replaces 'aria-live' usage and removes internal LiveRegion component

• #7267 1d8759a Thanks @lukasoppermann! - Used correct tokens for disabled radio control

• #7241 181f12e Thanks @francinelucca! - fix(LabelGroup): add role and aria-label to hidden items overlay

@primer/styled-react@1.0.2

Patch Changes

• #7261 13effb8 Thanks @joshblack! - Update exports from @primer/styled-react to be marked as deprecated

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

[TylerJDev]

@llastflowers, there will be some changes needed for release CI: https://github.com/github/github-ui/commit/3b1557f08ad7c1e6d8533bb0c80a9899d92c7021