chore(build): Add the GitHub token to Publish to NPM of Production Release

[DellaBitta]

Discussion

A previous security fix restricted which steps the GitHub token would have access to. Previously the GitHub token was configured in the checked step of .github/workflows/release-prod.yml and the subsequent steps would inherit it. But now, with persist-credentials: false, the token's TTL is only that one step.

But we need the token for the yarn release script as well.

This explictly sets the token using git commands, then runs yarn release and then removes the token.

Testing

CI

API Changes

None.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0fb557b

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