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]

Patch Changes

• #1757 9bc35cce Thanks @camertron! - Bump view_component to v2.81.0 to fix issue with Rails main

• #1753 95df035a Thanks @keithamus! - Update with_show_button slot to use Primer::Beta::Button instead of Primer::ButtonComponent.

• #1736 927a52c3 Thanks @dependabot! - Add format_style to RelativeTime component

• #1728 1c9981f4 Thanks @langermank! - Use a button tag for ActionList::Items

• #1750 64343de4 Thanks @jonrohan! - Adding :auto to size option to Dialog component

• #1756 280972cb Thanks @langermank! - Fix media query typo in Button

• #1754 d662c1c7 Thanks @keithamus! - Fix bug where clicking inside dialog, but finishing click outside, dismisses dialog

[github-actions]

❗ Pre-merge checklist

Please ensure these items are checked before merging.

🔎 Smoke test

Dotcom PR

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