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

• #2729 2b0a7bf Thanks @thesnowrose! - Fixes a bug where a tooltip was being shown in the navlist even when the text wasn't truncated for certain items.

• #2651 e1f3434 Thanks @jonrohan! - Add a slot to Overlay::Header called filter for a filter input.

Patch Changes

• #2735 507a743 Thanks @antn! - Explicitly convert params to integers where needed for several previews

• #2731 8123aee Thanks @jonrohan! - Remove old primitives color themes imports and only use V8 on the demo lookbook

• #2733 6fe410b Thanks @broccolinisoup! - Tooltip: Update the threshold value to match with the offset

[github-actions]

❗ Pre-merge checklist

Please ensure these items are checked before merging.

🔎 Smoke test

• All CI checks pass
• Lookbook opens in a browser
• Successful integration test with GitHub.com as a primary consumer of Primer View Components
  • Install the npm release candidate: npm i -w ./npm-workspaces/primer/ @primer/view-components@next
  • Update primer_view_components gem: script/vendor-gem https://github.com/primer/view_components.git -r changeset-release/main
  • 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.