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@38.28.0

Minor Changes

• #7888 45be31b Thanks @TylerJDev! - AnchoredOverlay: Extend cssAnchorPositioningSettings with a fallbackStrategy ('default' | 'none' | 'opposite-side') to control CSS anchor positioning fallback behavior when native CSS anchor positioning is active.

• #7923 6a7e130 Thanks @dylanatsmith! - Card: Add layout="compact" prop for a compact card layout with tighter spacing, no icon background, and smaller title

• #7922 55b7b04 Thanks @dylanatsmith! - InlineMessage: Make variant prop optional, defaulting to the standard foreground color with an info icon

• #7889 3af5edc Thanks @llastflowers! - Add data-component attributes and associated tests for PageHeader, PageLayout, Pagehead, Popover, Portal, and ProgressBar

• #7964 0f0f79f Thanks @TylerJDev! - AnchoredOverlay: Add cssAnchorPositioningSettings prop to allow opting out of native CSS anchor positioning (via disable), and use it in SelectPanel so the modal variant stays manually centered instead of being repositioned by CSS anchor positioning.

Patch Changes

• #7918 95986ce Thanks @jonrohan! - Autocomplete: Keep the typed text instead of restoring the full inline suggestion when the input loses focus, matching the behavior of pressing Escape

• #7971 2087e87 Thanks @francinelucca! - ThemeProvider: Skip rendering the SSR handoff script when the primer_react_theme_provider_remove_ssr_handoff feature flag is enabled

• #7910 0c38cfa Thanks @janmaarten-a11y! - Timeline: Add primer_react_timeline_list_semantics feature flag to opt into list semantics

  When the primer_react_timeline_list_semantics feature flag is enabled, Timeline renders as <ol role="list"> and Timeline.Item / Timeline.Break render as <li> so screen reader users get list navigation (total item count, position in sequence). The default behavior is unchanged — Timeline and its subcomponents still render as <div> until the flag is opted into.

  Enable the flag with the FeatureFlags provider:

  import {FeatureFlags} from '@primer/react/experimental'
  
  ;<FeatureFlags flags={{primer_react_timeline_list_semantics: true}}>
    <Timeline>…</Timeline>
  </FeatureFlags>

@primer/mcp@0.3.3

Patch Changes

• #7965 53ea013 Thanks @copilot-swe-agent! - MCP server: Add readOnlyHint annotation to all tools, allowing them to run without human-in-the-loop approval in agentic environments such as Copilot cloud agent.

• Updated dependencies [45be31b, 95986ce, 6a7e130, 55b7b04, 3af5edc, 2087e87, 0f0f79f, 0c38cfa]:

  • @primer/react@38.28.0

[github-actions]

❗ 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]

⚠️ Action required

👋 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. Check the integration testing docs for step-by-step instructions. Or, apply the integration-tests: skipped manually label to skip these checks.

To publish a canary release for integration testing, apply the Canary Release label to this PR.