Swap out secrets.GITHUB_TOKEN to allow releases

[friedbrice]

I noticed that the Github workflow that creates a release PR failed because of authentications issues. I think this is because the Repo is configured with my github personal access token. It's surfaced as secrets.GITHUB_TOKEN in workflow files.

Release PRs are automatically created with every merged PR.

alloglot/.github/workflows/release.yaml

Line 54 in 8ce931d

github_token: ${{ secrets.GITHUB_TOKEN }}

I think you can fix releases without making any changes to the workflow configs. It's been a while, but I think it goes like this.

1. Someone with push access to the repository create a github personal access token.
2. In the repository Settings > Secrets and variables > Actions > Environment secrets I think you will see one called GITHUB_TOKEN.
3. Replace the current GITHUB_TOKEN with the newly-created one.

The other secret needed to release is MARKETPLACE_TOKEN. I'm pretty sure that my token doesn't expire, so you shouldn't have to change that. However, if it is expired (or you just want to replace it), you can follow the steps here under Get A Personal Access Token and then replace the MARKETPLACE_TOKEN in the repo secrets.

[friedbrice]

@9999years and @josephsumabat and @Greg-Bm, thanks for continuing to work on this.

[josephsumabat]

I will get on this, thanks!

[josephsumabat]

I've updated the settings, should be addressed with #75 as well.

[josephsumabat]

@friedbrice your personal access token has expired. Would you mind unpublishing so we could re-publish under an updated token?