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/view-components@0.0.111

Patch Changes

• #1599 62dd9461 Thanks @simurai! - Move Popover styles to PVC

• #1605 63b40c1b Thanks @jonrohan! - Remove the deprecated Primer::CounterComponet and use Primer::Beta::Counter.

• #1611 047674c8 Thanks @safeforge! - Avoid double-registering of exported components

• #1601 ce2e959d Thanks @simurai! - Move flash styles to PVC

• #1607 c97f7b72 Thanks @simurai! - Move Avatar + AvatarStack styles to PVC

• #1598 040f4943 Thanks @simurai! - Move TimelineItem styles to PVC

• #1608 75ad4765 Thanks @mxriverlynn! - testing to ensure CSS classes used by PVC components are valid, according to the available selectors

• #1600 4501861b Thanks @simurai! - Move dropdown styles to PVC

[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 PR link
  • 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.