Skip to content

Conversation

@primer
Copy link
Contributor

@primer primer bot commented Dec 5, 2025

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/react@38.4.1

Patch Changes

@primer primer bot requested a review from a team as a code owner December 5, 2025 19:13
@primer primer bot requested a review from TylerJDev December 5, 2025 19:13
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

❗ Pre-merge checklist

Please ensure these items are checked before merging:

🔎 Smoke test

  • All CI checks pass on this pull request
  • Docs and Storybook open in a browser

🌏 Integration tests

  • Successful integration test with github/github-ui as a primary consumer of primer/react (automated pull request)
    • Verify all CI checks have passed on automated pull request
    • Manually test critical paths in preview
    • Manually test release-specific bugfixes and/or feature work as described in preview

✅ Peer Review

  • Create release review issue for Issues team (example)
  • Wait for approval from Issues team before merging

🤔 Sanity test

  • All bugfixes in this release have resolved their corresponding issues
  • The issues for any reverted PRs have been re-opened and commented on with a link to the reverted PR
  • No noticeable regressions have been introduced as a result of changes in this release
  • Release notes accurately describe the changes made

❗ Post-merge checklist

Please ensure these items are checked after merging:

🚢 Version upgrade, cleanup, and documentation

  • Upgrade @primer/react version at github/github-ui
  • Close Integration test PR and delete branch
  • Leave a /short-report comment on quarterly release conductor tracking issue summarizing time spent on release activities and any challenges encountered
  • Leave any testing notes on the automated per-shift release tracking issue. In particular, describe any issues encountered during your testing. This is helpful in providing historical context to the next release conductor as well as other maintainers.

@github-actions github-actions bot added the integration-tests: recommended This change needs to be tested for breaking changes. See https://arc.net/l/quote/tdmpakpm label Dec 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Or, apply the integration-tests: skipped manually label to skip these checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration-tests: recommended This change needs to be tested for breaking changes. See https://arc.net/l/quote/tdmpakpm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants