Release Tracking

[openproject-primer-view-components]

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

@openproject/[email protected]

Minor Changes

• #3776 edc480f Thanks @TylerJDev! - AvatarStack: Adds support for individual tooltips on AvatarStack component, avatars.

• #387 9f3c2aa Thanks @akabiru! - Add Primer::OpenProject::AvatarWithFallback component with client-side fallback rendering. When no image src is provided, renders an embedded SVG with user initials and consistent colors generated client-side by the AvatarFallbackElement web component. Extends Primer::Beta::Avatar without modifying upstream behavior.

• #3740 ccf3d94 Thanks @sarahkemi! - Add disable_expand param to AvatarStack for React component parity

[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 OpenProject as a primary consumer
  • Install the npm package locally
  • Install the primer_view_components gem locally
  • 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 OpenProject
• 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.