Use an app token for triggering a release

[aeisenberg]

We need to do this because using a default token will not recursively trigger a new workflow run.

The only way to test this is to merge to main and do a release.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

Comments skipped due to low confidence (1)

.github/workflows/post-release-mergeback.yml:166

• The new token generation step should be tested to ensure it works as expected. Consider adding a test workflow to validate the token creation process.

uses: actions/create-github-app-token@5d869da34e18e7287c1daad50e0b8ea0f506ce69

Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more

[henrymercer]

The indentation doesn't look quite right, but otherwise this looks good!

[aeisenberg]

Fixed the indentation. After merging, I will do a release to see if this fixes the problem.

[NlightNFotis]

Code-wise, this looks good.

The only question is whether the permissions are adequate for performing the release, but I guess we won't know until we try it.

[aeisenberg]

the permissions are adequate for performing the release

I believe so. We need contents: write for this to work. And the app provides it.