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

Minor Changes

• #2603 bbc1776 Thanks @langermank! - Tooltip visual refresh to match Primer React

• #89 0d06bec Thanks @HDinger! - Changes Primer::OpenProject::PageHeader:

  • Remove the context_bar_actions slot
  • Make breadcrumbs required
  • Remove the parent_link slot (will be derived automatically from the breadcrumb)
  • Change the slot definition for actions to be type specific (allowed types are: icon_button, button, link, text and menu)
  • On mobile, the actions collapse into a single action menu which is placed in the context_bar

Patch Changes

• #2706 60c5f01 Thanks @camertron! - Fix dialog CSS to prevent tooltip issues

• #2705 90192bb Thanks @langermank! - Revert "Swap bg-gradient with bg-color for Banner/Flash"

[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

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.