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

• #825 2c8e9240 Thanks @rezrah! - Switched to use CSS Logical Properties in compiled output.

  • Compiled styles now directly use CSS logical properties (e.g., margin-inline-start, margin-inline-end) instead of physical properties (margin-left, margin-right).
  • This change simplifies the stylesheet and reduces its overall size (652kB > 593kB)

  Example of the change:

  Source:

  .selector {
    margin-inline-start: var(--base-size-20);
  }

  Previous compiled output	New compiled output
  [dir='ltr'] .selector { margin-left: 2px; } [dir='rtl'] .selector { margin-right: 2px; }	.selector { margin-inline-start: 2px; }

Patch Changes

• #825 2c8e9240 Thanks @rezrah! - Fixed errors in compiled CSS stylesheets where selectors with special characters were being unintentionally escaped for compatibility with legacy browsers.

• #818 281beb08 Thanks @joshfarrant! - FormControl.Validation is now associated with the relevant input using aria-describedby.

• #822 75da350d Thanks @joshfarrant! - Updated IDEChatMessage type declaration to differentiate between assistant and user messages.

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

@primer/[email protected]

[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:
    • /features/copilot
    • /enterprise
    • /enterprise/advanced-security
    • /articles/security
    • /articles/security/what-is-security-testing
    • /features/preview
    • /features/copilot/getting-started and /features/copilot
    • /solutions/devops
    • /education
    • /mobile
    • /contact-sales
    • /about/diversity
  • 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 visual differences found

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

[rezrah]

Smoke test results

- FormControl.Validation is now associated with the relevant input using aria-describedby. 🟢

Tested in dotcom and one other subdomain site that uses form validations, works as expected. Example:

• Updated IDEChatMessage type declaration to differentiate between assistant and user messages 🟢

  No known usage of component yet, and the change is limited to pre-compile regressions of which none have been detected so far

- Fixed errors in compiled CSS stylesheets where selectors with special characters were being unintentionally escaped for compatibility with legacy browsers. 🟢

The :has selector being parsed as expected in dotcom. Issue verified as having been removed in compiled stylsheet/

- Switched to use CSS Logical Properties in compiled output. 🟢

Biggest change in this release, but with logical properties now part of Baseline browser support it's reasonable to roll this out. Dotcom doesn't consistently apply dir attribute too, which is an improvement to before as it applies the relevant styles regardless of reading direction.

Example:

Before	After

Release testing status: Ready to release 🟢