Skip to content
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

Improve releasing by merging npm and release jobs. #3390

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

danlapid
Copy link
Collaborator

@danlapid danlapid commented Jan 22, 2025

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.

@danlapid danlapid requested review from a team as code owners January 22, 2025 00:50
.github/workflows/release.yml Show resolved Hide resolved
.github/workflows/release.yml Show resolved Hide resolved
.github/workflows/release.yml Show resolved Hide resolved
.github/workflows/release.yml Show resolved Hide resolved
@fhanau
Copy link
Collaborator

fhanau commented Jan 22, 2025

@penalosa

Copy link
Collaborator

@fhanau fhanau left a 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.
@danlapid danlapid force-pushed the dlapid/improve_releasing branch from f8bcc0f to 9c3b5c7 Compare January 22, 2025 18:04
Copy link
Collaborator

@penalosa penalosa left a 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!

@danlapid danlapid merged commit e35b547 into main Jan 22, 2025
17 checks passed
@danlapid danlapid deleted the dlapid/improve_releasing branch January 22, 2025 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants