Test against @castleio/sdk 3.1.0 from a vendored tarball#9
Closed
bartes wants to merge 1 commit into
Closed
Conversation
Install the SDK from a prebuilt `3.1.0` tarball under `vendor/` so the demo can run against the new release before it is published to npm. The README documents switching the dependency back to the registry version (`^3.1.0`) and removing the tarball once it is published.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Runs the demo against the new Castle Node SDK release ahead of its npm publish.
@castleio/sdkfrom a prebuilt3.1.0tarball undervendor/(referenced viafile:), since the SDK builds to a gitignoreddist/and can't be installed from a Git tag directly.^3.1.0) and removing the tarball once it is published.