fix(ci): remove build step when publishing typescript-bindings #1096
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
Removed the
npm build
step ontypescript-bindings
npm publish CI jobMotivation and Context
On #1093 we introduced a step to build the npm package for both
wallet_jrpc_client
andtypescript-bindings
.We shouldn't include that step for
typescript-bindings
as we can assume it's already built (there are checks for that) and the build runs a custom script that builds all of the rust project using cargo.So this PR removes the
npm build
step ontypescript-bindings
npm publish CI job. We only need it forwallet_jrpc_client
How Has This Been Tested?
Does not apply
What process can a PR reviewer use to test or verify this change?
Does not apply
Breaking Changes