Migrate PAT GitHub Token Usage

[petertonysmith94]

Summary

Usage of the personal access token has now been removed therefore we need to migrate to an alternative means of authentication. All instances of REPO_TOKEN within our workflows need to change.

Some possible workarounds.

Usages

• release.yaml (failure)

fuels-ts/.github/workflows/release.yaml

Lines 27 to 29 in 79ffb82

	# workaround to ensure force pushes to changeset branch use REPO_TOKEN owner's account
	# see https://github.com/changesets/action/issues/70
	persist-credentials: false

• pr-validate-changesets.yaml

fuels-ts/.github/workflows/pr-validate-changesets.yaml

Lines 49 to 55 in 71220b5

	- name: Set up .netrc file
	if: env.CHANGESET_FILE == ''
	run: |
	echo "machine github.com" > $HOME/.netrc
	echo "login github-actions[bot]" >> $HOME/.netrc
	echo "password ${{ secrets.REPO_TOKEN }}" >> $HOME/.netrc
	chmod 600 $HOME/.netrc

• linear-pr-integration.yaml

fuels-ts/.github/workflows/linear-pr-integration.yaml

Line 17 in 79ffb82

github_token: ${{ secrets.REPO_TOKEN }}

[arboleya]

I think we can start by using GITHUB_TOKEN everywhere.

Then we should make a list of:

1. Things that stopped working (npm releases?)
2. Automations that started requiring manual interventions (workflow approvals?)

With this list at hand, we can reasses things in isolation and discuss next resolution steps.

[petertonysmith94]

I believe we're going to require an GitHub application long-term:

• https://github.com/actions/create-github-app-token

[arboleya]

Great find!

[petertonysmith94]

@arboleya I've gone over all the token usages and attempted to identify the possible permissions that a potential application might require.

I've summarised potential next steps within the following PR:

• chore: use GitHub application token #3616