Release Tracking

[openprojectci]

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

Minor Changes

• #3676 263b185 Thanks @TylerJDev! - Utilize modern Tooltip component for AvatarStack

• #3700 7c72ee7 Thanks @TylerJDev! - SelectPanel: Prevents keydown events from escaping the SelectPanel when within the items.

Patch Changes

• #3692 b0acdff Thanks @lukasoppermann! - Replacing color tokens for StateLabel draft with new draft tokens

• #3659 6734331 Thanks @bsatarnejad! - Add custom label support for ToggleSwitch on/off states

• #3723 e545103 Thanks @jonrohan! - Add box-shadow back to the AvatarStack avatars

• #3686 db729fb Thanks @langermank! - Implement forced colors for progress bar

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