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]

Minor Changes

• #6470 e53228c Thanks @dylanatsmith! - Add size prop to ActionList.LinkItem component. The size prop accepts 'medium' (default) or 'large' values and provides the same styling options as ActionList.Item for consistent sizing across ActionList components.

• #6265 829a933 Thanks @joshblack! - Update IssueLabel component types to support custom content through children and support the as prop

• #6420 024b82a Thanks @chanakyav! - Adds variant and shape props to AvatarStack component. The variant prop will allow the component to render in a cascade view (by default) or a new stacked view which will evenly space the avatars and remove opacity. The shape prop will allow the avatars to be rendered as circles (by default) or squares.

• #4744 3c9e322 Thanks @TylerJDev! - Address additional ToggleSwitch a11y feedback

• #6182 9e49abd Thanks @TylerJDev! - Textarea: Adds minHeight and maxHeight as props

Patch Changes

• #6330 fbdcac4 Thanks @francinelucca! - feat(SelectPanel): remove aria activedescendant and add a roving tab index

• #6365 ae4dd07 Thanks @langermank! - Add width: 100% to Portal

@primer/[email protected]

Minor Changes

• #6417 0ce5db8 Thanks @joshblack! - Create the @primer/styled-react package to help with bridging between styled-components and Primer React

[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	90.2 KB (0%)
packages/react/dist/browser.umd.js	90.38 KB (0%)

[hectahertz]

✨