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/react-brand@0.73.0

Minor Changes

• #1425 a486555 Thanks @danielguillan! - Added the new MinimalVideoPlayer component for presenting muted, looping videos with a minimal play and pause control.

  <MinimalVideoPlayer poster="/video-poster.jpg" src="/video.webm" title="Product interface demonstration" />

  🔗 See MinimalVideoPlayer documentation for more usage examples

Patch Changes

• #1432 e8b64f0 Thanks @rezrah! - Allow ButtonGroup to accept conditionally rendered children.

  Example:

  <ButtonGroup>
    <Button>Primary action</Button>
    {showSecondaryAction ? <Button>Secondary action</Button> : null}
  </ButtonGroup>

• #1438 baa0861 Thanks @rezrah! - Added configurable Card.Image padding, which allows for full-bleed images to be displayed.

  Example:

  <Card hasBorder>
    <Card.Image padding="none" {...rest} />
  </Card>

• #1439 bca51bc Thanks @danielguillan! - Update expressive Testimonial typography, spacing, and responsive composition to match the design.

• #1439 bca51bc Thanks @danielguillan! - Added width: 100% to all River components to fix layout regression on tablet viewports

• #1428 8ac13c8 Thanks @danielguillan! - Updated Card responsive spacing, exposed arrow CTA labels on non-hover devices, and removed the hover scale effect.

• #1441 8040f9a Thanks @rezrah! - Updated the FAQ gridline variant to include inline padding by default for narrow viewports.

@primer/brand-primitives@0.73.0

Patch Changes

• #1438 baa0861 Thanks @rezrah! - Added configurable Card.Image padding, which allows for full-bleed images to be displayed.

  Example:

  <Card hasBorder>
    <Card.Image padding="none" {...rest} />
  </Card>

@primer/brand-mcp@0.73.0

Patch Changes

• #1438 baa0861 Thanks @rezrah! - Improved gridline guidance. Also added new example CSS with canonical component examples to the catalog.

@primer/brand-css@0.73.0

@primer/brand-docs@0.73.0

@primer/brand-storybook@0.73.0

@primer/brand-e2e@0.73.0

@primer/brand-fonts@0.73.0

@primer/brand-config@0.73.0

[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-ui, as a primary consumer of Primer Brand
  • Install RC: npm install @primer/react-brand@{RC_VERSION} -w @github-ui/swp-core
  • Run development server
  • Manually verify release-specific bugfixes and/or features on the following pages:
    • /home
    • /features/copilot
    • /features/copilot/plans
    • /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]

🟢 Bundle size report

Check	Main	Branch	Change
UMD — full bundle (JS)	102.63 kB	102.63 kB	🟢 No change
UMD — full bundle (CSS)	68.11 kB	68.11 kB	🟢 No change
ESM — full bundle (JS + CSS)	1.60 MB	1.60 MB	🟢 No change
ESM — tree-shaken simple (Button)	71.35 kB	71.35 kB	🟢 No change
ESM — tree-shaken complex (ActionMenu)	80.31 kB	80.31 kB	🟢 No change

[github-actions]

⚠️ Visual differences found

Our visual comparison tests found UI differences.

Please review the differences by using the test artifacts to ensure that the changes were intentional.

Artifacts can be downloaded and reviewed locally.

Download links are available at the bottom of the workflow summary screen.

Example:

If the changes are expected, please run npm run test:visual:update to replace the previous fixtures.

Review visual differences

[rezrah]

Smoke test results

RC was tested in Dotcom and Storybook. All checks passing. One notable, albeit unrelated font rendering issue observed in dev environment, more on that below.

• 🟢 New MinimalVideoPlayer

  Verified it works correctly without error in dotcom Storybook and Flex Suite.

  The bulk of custom code in VideoHosted.tsx can be removed by using this Primer component now. cc. @rfearing @stefankp

Before	After

• Allow ButtonGroup to accept conditionally rendered children 🟢

  Tested in Storybook, works as expected.

• Update expressive Testimonial typography, spacing, and responsive composition to match the design 🟡

  Outer padding is now added to the component variant. This means the template-specific padding via Box is now redundant and will need removing as it's now too large. ⚠️ This needs to be fixed during the upgrade ⚠️.

  Before	After

• Added width: 100% to all River components to fix layout regression on tablet viewports 🟢

  No observed regressions to Rivers. Still working as expected on tablet. 🟢

• Updated Card responsive spacing, exposed arrow CTA labels on non-hover devices, and removed the hover scale effect. 🟢

  The new card image variant (full-bleed) works as expected. The required update in FlexSuiteLargeCards.tsx is to:

  • Remove variant="minimal"
  • Add hasBorder
  • Add padding="none"

  This should fix the cards to match expected designs. cc. @stefankp @rfearing @natalierharris

  Before	After

• Updated the FAQ gridline variant to include inline padding by default for narrow viewports 🟢

  Gridline variants now include spacing by default. Tested in Dotcom (FlexSuite).

  Before	After

• Issue unrelated to design, but relevant for upgraders.

  Dev environment wasn't loading Mona Sans fonts correctly. Following ESM change, the fonts were routing through webpack js transpiler and not css. As a result, by default the font was loading in Menlo fallback.

  

Release testing status: Ready to release 🟢