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.
Description of the change
This is an attempt at simplifying the CI workflows. Instead of using two jobs for CI, it switches to one. We used two because we used to compile the plugin with MacOS but do the CLI integration testing with Linux. But now we compile the plugin with Linux so we can reuse the same job. I've also moved the WPT tests because they can just re-use the same artifact we've built in the CI pipeline to run the WPT test suite so we don't need a separate workflow. We used to need a separate one because the WPT test suite required Javy to be built with an
experimental_event_loop
feature enabled but that's not the case any more. I've also inlined the shared CI setup since there's only one user of it now.Why am I making this change?
Less workflows to manage and reducing the jobs from two to one should speed up CI a bit.
Checklist
javy-cli
andjavy-plugin
do not require updating CHANGELOG files.