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

• #295 48d3acd Thanks @HDinger! - Introduce the TreeView component

Patch Changes

• #295 48d3acd Thanks @HDinger! - Remove overridden capture method in forms code.

• #295 48d3acd Thanks @HDinger! - Update the SelectPanel no results pane to a smaller height

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

[HDinger]

Hi @camertron

@myabc and I found the reason for the failing release CI. The Changeset team introduced a bug some days ago in this commit. Basically they switched from

git push origin --tags
to
git push origin v.0.65.0

The first one just does nothing when there is no local tag while the second creates a failure and stops the execution.
Alex creates an issue in their repo and we will wait for their response. There is already an issue, and Alex will leave a comment. We will wait a bit and see whether they react. If not, we will create the tag manually in the changset-publish script. Then we should be able to release again.

[myabc]

@camertron @HDinger my comment basically reiterates what @HDinger stated in this PR.

[camertron]

Hey @HDinger and @myabc, nice work tracking down the issue! I will say, this is not the first time the changesets tool has exhibited weird behavior 😬

[HDinger]

I also left a comment in the upstream PVC repo.