Repository navigation
fix: build with tish 4.0.1 - #3
Merged
Merged
Conversation
The tish 3.x crates accept any later version of each other, so with 4.x on crates.io a site built on tish 3 can link two tishlang_core copies. Orbit, its template and its peer range now use tish 4.0.1.
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.
Moves Orbit to tish 4.0.1, the line moo and the other tishlang projects are now on:
devDependencies:@tishlang/tish4.0.1 and@tishlang/tish-lint^4.0.1.>=4.0.1.@tishlang/tishis 4.0.1.The tish 3.x crates on crates.io require each other as
>=0.1. With 4.x published, a native build on tish 3 can link twotishlang_corecopies.Checked locally:
npm run lintis clean.npm testpasses (25).npm run test:e2epasses.