-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update dependencies, use ncc
to bundle actions logic
#59
Conversation
54ef47e
to
22a67e3
Compare
0ca61c6
to
34aa7df
Compare
…endencies into standalone files
34aa7df
to
b323fbc
Compare
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.
Minor suggestions for RELEASE.md.
- Run `git tag -s "<TAG>" -m "<TAG>" && git push origin "<TAG>"`. | ||
- Merge the pull request. |
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.
This appears to be out of order, as it's going to happen after the tag is made.
This should probably include a git checkout main && git pull
after the PR is merged, to ensure that the local main
branch is up to date before making the tag.
If you want to get even fancier, you can steal this which will for creating the tag even if the name of the remote is not origin
(which is often the case for me).
I updated the dependencies in order to resolve #58, but the diff was huge because of the need to include node_modules in the repository.
Following best practices that I found in other GitHub Actions, I've added a build step that uses
@vercel/ncc
to bundle dependencies and logic into single JS files for each action.