ci(actions): trying to auto upgrade swc_* #117
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
I can offer my gh token to get notified myself, please let me know. |
kdy1
approved these changes
Dec 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR trying to experiment automated action to create a PR to upgrade swc_* when new version is released. It is an action runs periodically (2 times a daily) which runs
cargo upgrade, then create a PR if there's an update to be applied. If there is an open PR with specific branch name, it won't create new but trying to update PR with new commit when there's an update.To create fully working pull request, action requires personal access token unfortunately. I choose name
GHA_UPGRADE_TOKENfor those, having one under repository secrets will enable action to perform:We can use default
GITHUB_TOKENstill, but it'll create PR with limited acesss with github-actions bot will not trigger any action to verify build is passing or not. (ref: peter-evans/create-pull-request#48)My goal is let these actions run across transitive deps we own, so most of upgrade process is simple enough to click merge btn unless there are breaking changes.