Update to use PAT
to avoid rate limits and update build environment
#68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changeset updates the build script to use a
PAT
secret to avoid secondary rate limits and updates the build environment. Each PAT has a rate limit of 5000 requests/h while theGITHUB_TOKEN
has a rate limit of 1000 requests/h (https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-github_token-in-github-actions).I've already assigned a read-only
PAT
for the @reactphp-bot user for this repository. This secret should be available to the build script after this PR is merged. This means that the PR may currently fail to build, but should work regardless once merged. I've assigned the same PAT to my fork to confirm this works as expected. Once merged, the build should now work again and finally deploy all releases published since #67 was reported.Resolves / closes #67
Builds on top of #53 and #65