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

Patch Changes

• #3912 1597a74 Thanks @llastflowers! - Remove newline in file to revert accidental visual regression of Button

• #3894 4ddf815 Thanks @francinelucca! - chore(treeview): add treeitem role to shadow dom node

• #3919 e060f4d Thanks @francinelucca! - Chore: add custom "invokerClicked" selectpanel event

• #3930 0ebf631 Thanks @copilot-swe-agent! - Update Catalyst to version 1.8.0 and hard-code controller/custom-element names via their @controller('...') decorators to allow for better minification

[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

🚢 Post ship reminders

• Deploy lookbook via chat ops in the #primer-rails-ops channel. .deploy primer-lookbook to production

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.