-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release please config updates #229
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@@ -7,8 +7,8 @@ name: release-please | |||
jobs: | |||
release-please: | |||
runs-on: ubuntu-latest | |||
permissions: | |||
contents: write | |||
pull-requests: write | |||
steps: | |||
- uses: google-github-actions/release-please-action@v4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- uses: google-github-actions/release-please-action@v4 | |
- uses: google-github-actions/release-please-action@v4 | |
with: | |
token: ${{ secrets.GITHUB_TOKEN }} |
IIRC, I set the token so that the release PR triggers CI workflows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I have seen this be an issue before. I thought that secrets.GITHUB_TOKEN
was the default token so it wouldn't trigger CI workflows, and it would need to pass in a different PAT for that to work.
If this is an issue we can try adding back the token.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. Workflows didn't run for #218
I think this fixes the issues with the
release-please
workflow failing after #225.It matches mostly what we have in https://github.com/nodejs/node-gyp