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/[email protected]

Minor Changes

• #3041 14dd0d3 Thanks @HDinger! - Support leading and trailing icons for Links

• #3219 633bd05 Thanks @camertron! - Removing the validate classname check that forces system arguments instead of utility classes

Patch Changes

• #3217 0bbb076 Thanks @camertron! - Fix issue causing AutoComplete elements to overflow their container

• #3205 79ca4f9 Thanks @camertron! - Ensure full_width: option is respected by the auto_complete input

• #3202 a574b0e Thanks @camertron! - Prevent hidden inputs from taking up space on the page

• #3216 23dd4fa Thanks @keithamus! - Remove redundant code for better performance.

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