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

• #1583 a06f52cf Thanks @jonrohan! - Migrating progress bar component to beta folder, and adding progress bar css.

• #1579 05e07bb1 Thanks @camertron! - Move Banner to alpha namespace

• #1592 f743267e Thanks @simurai! - Move Breadcrumbs styles to PVC

• #1584 cad5c235 Thanks @simurai! - Move blankslate styles to PVC

• #1574 b3e351d2 Thanks @mxriverlynn! - adding a test suite to show all component-specific selectors are used in previews, and updating various component previews for lookbook

• #1587 ac54ecc4 Thanks @simurai! - Move labels styles to PVC

• #1594 55f0d4df Thanks @simurai! - Move Subhead styles to PVC

• #1593 7042b5f5 Thanks @simurai! - Move ToggleSwitch styles to PVC

• #1590 820022c3 Thanks @simurai! - Move Truncate 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
  • 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.

[camertron]

See: https://github.com/github/github/pull/246333