Skip to content

fix: use REPO_ACCESS_TOKEN for library docs release#845

Closed
Dan Miller (milldr) wants to merge 0 commit into
masterfrom
milldr/docs-build-speedup
Closed

fix: use REPO_ACCESS_TOKEN for library docs release#845
Dan Miller (milldr) wants to merge 0 commit into
masterfrom
milldr/docs-build-speedup

Conversation

@milldr
Copy link
Copy Markdown
Member

what

  • Use REPO_ACCESS_TOKEN instead of GITHUB_TOKEN for creating/deleting the library-docs-latest release

why

The generate-library.yml workflow failed with:

HTTP 422: Validation Failed
Repository rule violations found
Cannot create ref due to creations being restricted.

GITHUB_TOKEN doesn't have permission to bypass repository tag protection rules. REPO_ACCESS_TOKEN (PAT) has elevated permissions that can bypass these restrictions.

references

  • Fixes the "Package and Release" step failure in the Generate Library workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant