-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve releasing by merging npm and release jobs. #3390
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.
Looks reasonable to me otherwise – I think it's easy to get the file paths wrong when downloading workerd/uploading the binary but I didn't see any issue here.
Merge npm.yml and npm-types.yml into the release workflow. This will remove the neccessity to run the npm and npm-types jobs manually.
f8bcc0f
to
9c3b5c7
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.
Looks reasonable to me. We'll know for sure after trying to run a release, but this'll really speed up the process!
Merge npm.yml and npm-types.yml into the release workflow.
This will remove the necessity to run the npm and npm-types jobs manually.
There can be further work done to remove duplication of bazel setup inside of this file and with the _bazel.yml file.
That improvement does not need to block this PR as this PR does not make this problem any worse than it was before.
There are other similar improvements that can honestly be done in this file that I also punted from achieving in this PR.
The fact that this entire file runs only on release makes it really hard to iterate and I'd rather change as little as possible.