Remove javy-cli from NPM publishing workflow #733
Merged
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
Updating the NPM package publishing workflow to remove
javy-cli
from it.Why am I making this change?
I should've done this as part of #726 but I missed it in the search results (there's also a lot of references to the
javy-cli
crate in a bunch of places). At the moment this is causing a GitHub Action failure after merging to the main branch.Checklist
javy-cli
andjavy-core
do not require updating CHANGELOG files.