Release Tracking

[primer-css]

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

• #2187 ce2011e6 Thanks @camertron! - Expose ActionList's #build_item and #build_avatar_item externally to facilitate parent-less item construction

• #2188 5950afea Thanks @camertron! - Allow disabling submit buttons

• #2165 1b8ff1b7 Thanks @camertron! - Add an accessible avatar item to ActionList, NavList, and ActionMenu

• #2186 eab82c07 Thanks @camertron! - On dismiss, allow banners to be hidden instead of removed from DOM

Patch Changes

• #2164 93344455 Thanks @camertron! - Allow form buttons to be disabled on click with data-disable-with

• #2158 0afaecc6 Thanks @jonrohan! - Fix bug in ActionMenu button where return doesn't trigger menu

• #2168 45822328 Thanks @keithamus! - Guard tooltip popover calls from Failed to execute 'showPopover' on 'HTMLElement': Not supported on elements that do not have a valid value for the 'popover' attribute.

• #2160 8464823b Thanks @langermank! - Fix Dialog backdrop color fallback

• #2163 e3aeda1f Thanks @langermank! - Add fallbacks for primary Button

• #2170 4391873d Thanks @Tonkpils! - Add support for capitalize to text-transform

• #2169 4f11f5e3 Thanks @camertron! - Fix color contrast issues for action list hover state (danger style)

[github-actions]

❗ Pre-merge checklist

Please ensure these items are checked before merging.

🔎 Smoke test

• All CI checks pass
• Docs and Lookbook open in a browser
• Successful integration test with GitHub.com as a primary consumer of Primer View Components
  • Install the npm release candidate in npm-workspaces/primer/
  • Use bin/vendor-gem to update primer_view_components gem
  • Verify no new build errors appear
  • Verify no new linting errors appear
  • Manually test critical paths
  • Manually test release-specific bugfixes and/or features work as described

🤔 Sanity test

• All bugfixes in this release have resolved their corresponding issues
• All new features in this release have been tested and verified as compatible with GitHub.com
• No noticeable regressions have been introduced as a result of changes in this release
• Release notes accurately describe the changes made

Please also leave any testing notes as a comment on this pull request. In particular, describing any issues encountered during your testing. This is helpful in providing historical context to maintainers.

[jonrohan]

dotcom release https://github.com/github/github/pull/282537