Fix failing GitHub Actions job 'Main'

[Copilot]

There seems to be an issue in the release workflow with the move to Node.js v26, trying this out as a fix 🤞

[changeset-bot]

⚠️ No Changeset found

Latest commit: bb09e73

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[joshblack]

@copilot revert the changes to react deps

[Copilot]

@copilot revert the changes to react deps

Addressed in bb09e73.

[Copilot]

Pull request overview

This PR aims to unblock the failing Release → “Main” GitHub Actions job after the move to Node.js v26, by adjusting the release workflow’s Changesets behavior and aligning the repo lockfile with the current workspace package version.

Changes:

• Update the release workflow to run changesets/action in commitMode: github-api (avoids relying on git push credentials in the runner).
• Refresh package-lock.json entries so workspace/example references to @primer/react match the current 38.29.0 version.

Show a summary per file

File	Description
package-lock.json	Aligns lockfile entries for @primer/react to 38.29.0 to keep installs (npm ci) consistent with workspace versions.
.github/workflows/release.yml	Switches Changesets action commit strategy to github-api for the main release job.

Copilot's findings

• Files reviewed: 1/2 changed files
• Comments generated: 0