Release Tracking

[primer]

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

@primer/[email protected]

Patch Changes

• #3498 e9a4a60 Thanks @joelhawksley! - Update test allocations to match latest ViewComponent alpha release.

• #3483 1165454 Thanks @HDinger! - Provide default id for clear button in text fields

• #3475 28532ae Thanks @langermank! - Bump primitives + update snapshots

[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 GitHub.com as a primary consumer of Primer View Components
  • Install the npm release candidate: npm i -w ./npm-workspaces/primer/ @primer/view-components@next
  • Update primer_view_components gem: script/vendor-gem https://github.com/primer/view_components.git -r changeset-release/main
  • 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 GitHub.com
• 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 Primer team,

I just wanted to share an insight that we spent quite some time on when trying to release our PVC fork. Currently, there are some issues with releasing, which will most likely affect you as well.
The changeset team has recently updated their release action in commit changesets/action@207dc3d . Basically they switched from

git push origin --tags

to

git push origin {{tagName}}

The first one just does nothing when there is no local tag while the second creates a failure and stops the execution. See for example our latest release run.

So we will either use an older version of changeset or update the changeset-publish script to create a local tag before trying to push it. I hope that this will help you and save some time.