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

Minor Changes

• #2884 85f6a01 Thanks @owenniblock! - Adds default sr-only text to spinner component

• #2855 05159ca Thanks @keithamus! - Upgrade @github/tab-container, using shadowdom

• #2887 5589bcf Thanks @HDinger! - Add support for target attribute on links of Primer::Beta::Breadcrumbs

• #2895 bb1a15b Thanks @camertron! - Add a leading spinner to the TextField component.

Patch Changes

• #2872 5445f2e Thanks @smockle! - chore: Update '@github/relative-time-element' from 4.4.0 to 4.4.1

• #2885 37727e3 Thanks @camertron! - Fix ActionMenu item activation by using PointerEvent instead of MouseEvent and KeyboardEvent.

• #2904 96307bf Thanks @camertron! - Fix CSS issue causing scrollbars to appear in tabs

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