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

Patch Changes

• #1187 168a187 Thanks @rezrah! - No-op upgrade to our internal linting toolchain (ESLint v9), which affects the source code organization of this package. No functional impact is expected.

@primer/brand-css@0.59.2

@primer/brand-primitives@0.59.2

@primer/brand-docs@0.59.2

@primer/brand-storybook@0.59.2

@primer/brand-e2e@0.59.2

@primer/brand-fonts@0.59.2

@primer/brand-config@0.59.2

[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

[Copilot]

Pull Request Overview

This PR represents a version bump from 0.59.1 to 0.59.2 across all packages in the Primer Brand monorepo. The release includes a patch update related to an ESLint v9 upgrade that affects source code organization without functional impact.

• Version bumped from 0.59.1 to 0.59.2 across all workspace packages
• CHANGELOG entries added for version 0.59.2 across all packages
• The consumed changeset file (.changeset/spotty-geckos-cry.md) has been removed as part of the release process

Reviewed Changes

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

Show a summary per file

File	Description
packages/repo-configs/package.json	Version bump to 0.59.2
packages/repo-configs/CHANGELOG.md	Added 0.59.2 section
packages/react/package.json	Version bump to 0.59.2
packages/react/CHANGELOG.md	Added 0.59.2 section with ESLint v9 upgrade notes
packages/fonts/package.json	Version bump to 0.59.2
packages/fonts/CHANGELOG.md	Added 0.59.2 section
packages/e2e/package.json	Version bump to 0.59.2
packages/e2e/CHANGELOG.md	Added 0.59.2 section
packages/design-tokens/package.json	Version bump to 0.59.2
packages/design-tokens/CHANGELOG.md	Added 0.59.2 section
packages/css/package.json	Version bump to 0.59.2
packages/css/CHANGELOG.md	Added 0.59.2 section
apps/storybook/package.json	Version bump to 0.59.2
apps/storybook/CHANGELOG.md	Added 0.59.2 section
apps/next-docs/package.json	Version bump to 0.59.2 and updated dependencies
apps/next-docs/CHANGELOG.md	Added 0.59.2 section
.changeset/spotty-geckos-cry.md	Removed changeset file (consumed during release)

[github-actions]

🟢 No design token changes found

[github-actions]

🟢 Unit test coverage changes found

Unit test coverage has been updated through this PR.

Changes: 0 new tests, 0 removed tests, 1 improved, 0 decreased

Component/Hook	Statements	Functions	Branches	Change
SubdomainNavBar	71.8% 72.5%	79.4% 82.4%	70.3%	+2.9%

[github-actions]

🟢 No visual differences found

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

[danielguillan]

Smoke test results

• Upgrade to eslint v9 🟢
  No-op uptdate. No issues, regressions or new console warnings found.

Release testing status: Ready to release 🟢