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
ci: use GITHUB_TOKEN instead of PAT #1017
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.
As discussed in slack:
a PAT is needed if the branch that auto commits to is protected . If we leave the branch unprotected, it won't be needed.
https://github.community/t/how-to-push-to-protected-branches-in-a-github-action/16101/10
Since stable
is unprotected (check: https://a.cl.ly/nOu5Q7L9 ), this should work.
@@ -26,7 +26,8 @@ jobs: | |||
run: yarn --frozen-lockfile | |||
|
|||
- name: Create release | |||
run: npm run release |
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.
Wondering if using yarn run release
might have better results than npm run release
, noticed we are seeing the cleanup error in CI again https://github.com/vega/ts-json-schema-generator/runs/4232722268?check_suite_focus=true
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.
Let's try in f5848fa
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.
🚀 PR was released in |
📦 Published PR as canary version:
0.97.1--canary.1017.a612074.0
✨ Test out this PR locally via:
npm install ts-json-schema-generator@0.97.1--canary.1017.a612074.0 # or yarn add ts-json-schema-generator@0.97.1--canary.1017.a612074.0