Release tracking

[primer-css]

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]

Minor Changes

• #1151 3e39ae1 Thanks @rezrah! - Updated the minimum Node.js dependency for @primer/react-brand to match the current LTS version: v22

  Also updated webpack and various other internal dependencies.

• #1132 072f640 Thanks @rezrah! - Added new Tabs component.

  Example:

  <Tabs {...args} aria-label="Tabs">
    <Tabs.Item>Tab one</Tabs.Item>
    <Tabs.Item>Tab two</Tabs.Item>
  
    <Tabs.Panel>
      <Text>Panel one</Text>
    </Tabs.Panel>
    <Tabs.Panel>
      <Text>Panel two</Text>
    </Tabs.Panel>
  </Tabs>

Patch Changes

• #1133 23a0d50 Thanks @joshfarrant! - Added some comments to the Accordion component. This is a no-op update.

• #1132 072f640 Thanks @rezrah! - Updates to useTabs hook:

  • Added an optional externalRef parameter to getTabProps function for improved forwardRef support.
  • Fixed onTabActivate callback to only trigger when switching between tabs (not on initial mount)
  • Optimized focus state management by preventing unnecessary state updates when focus doesn't change.
  • Removed redundant state updates in focusTab and onTabFocus functions

  This affects the following components, which use this hook:

  • Tabs component
  • IDE component

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

[Copilot]

Pull Request Overview

This is an automated release tracking PR generated by the Changesets action to bump all package versions to 0.57.3. The release includes a minor documentation update to the Accordion component with added comments.

Key Changes

• Version bump from 0.57.2 to 0.57.3 across all packages in the monorepo
• Updated dependency references in the docs app to use the new version
• Consumed the changeset file for the Accordion component update

Reviewed Changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated no comments.

File	Description
packages/*/package.json	Version bump to 0.57.3 for all packages
packages/*/CHANGELOG.md	Added 0.57.3 section to all changelog files
apps/next-docs/package.json	Updated internal dependency versions to 0.57.3
.changeset/five-goats-march.md	Removed consumed changeset file for Accordion update

[github-actions]

❗ Pre-merge checklist

Please ensure these items are checked before merging.

✅ Preliminary checks

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

🔌 Integration smoke tests

Dotcom

• Performed successful integration test with github/github, as a primary consumer of Primer Brand
  • Install RC: bin/npm install --save --save-exact @primer/react-brand@{RC_VERSION}
    Important: Verify that each workspace package has been updated correctly in their respective package.json files
  • Run development server
  • Manually verify release-specific bugfixes and/or features on the following pages:
    • /home
    • /features/copilot
    • /features/copilot/tutorials
    • /features/preview
    • /enterprise
    • /enterprise/contact
    • /security/advanced-security
    • /education
    • /mobile
    • /about/diversity
    • /newsroom
    • /resources/articles
    • /resources/articles/software-development
    • /resources/articles/software-development/what-is-cloud-native
    • /resources/whitepapers
    • /resources/whitepapers/how-the-c-suite-can-lead-ai-innovation
    • /solutions
    • /solutions/use-case/
    • /solutions/use-case/devops
    • /contentful-lp-tests/flex-example-dark (requires a flag)
    • /contentful-lp-tests/flex-example-light (requires a flag)
  • Manually compare production site to local instance for any non-release specific regressions

Subdomain sites

• Performed successful integration test with githubuniverse.com, as a Tier 1 consumer of Primer Brand outside of the monolith.

  • Run development server and verify no new console warnings or regressions are found
  • Run local build to verify the release compiles correctly
  • Manually performed side-by-side comparison with production

• Performed successful integration test with https://resources.github.com/, as a Tier 1 consumer of Primer Brand outside of the monolith.

  • Run development server and verify no new console warnings or regressions are found
  • Run local build to verify the release compiles correctly
  • Manually performed side-by-side comparison with production

Sandboxes

• Works in CodeSandbox or StackBlitz
  • New components render successfully
  • (optional) Tested in both SPA and SSR apps if release contains build changes

🤔 Cross-check (aka sanity test)

• Release notes accurately describe the changes made
• All bugfixes in this release have resolved their corresponding issues
• The issues for reverted PRs have been re-opened and commented on with a link to the reverted PR
• No noticeable regressions or side-effects have not been introduced as a result of changes in this release.
  • If they have, determine severity of the issue and consider hotfixing

After tests

• Add report summary of your findings, including any images. Use following template as a guide:

  #### Smoke test results
  
  - Feature 1 🟢 🟡 🔴 (choose one, depending on success levels)
  
    {insert screenshot}
  
  Release testing status: Ready to release 🟢 | Paused 🟡 🔴 (choose one and provide reason)

🚢 After merge

• Issue release comms in primer brand Slack channel
• Add the preview deployment's link to releases as a way of permalinking to old version's docs. Example

[github-actions]

🟢 No design token changes found

[github-actions]

🟢 No unit test coverage changes found

All components and hooks with tests maintain the same coverage as the main branch.

[github-actions]

🟢 No visual differences found

Our visual comparison tests did not find any differences in the UI.

[jonrohan]

Testing approval to see if it still requires brand-reviewers

Edit: Looks like it works! This is what I see now