Fix release changelog generation on Node.js v26

[Copilot]

The Release workflow is failing on main after moving to Node.js v26. Changesets changelog generation can hit GitHub GraphQL gzip stream failures and exit before updating the release PR.

Changelog

New

• Local Changesets changelog generator for release automation.

Changed

• Changesets config now uses the local generator.
• GitHub GraphQL changelog lookups now:
  • request identity encoding
  • disable node-fetch compression when applicable
  • retry transient stream/API failures
  • avoid logging sensitive response details

Removed

• N/A

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; release workflow tooling only.

Testing & Reviewing

Review focus:

• Changelog output parity with @changesets/changelog-github
• Node.js v26 stream workaround scope
• GitHub API error handling and log safety

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github-ui (Learn more about how to run integration tests)

[changeset-bot]

⚠️ No Changeset found

Latest commit: cbd0d90

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