fix(ci): generate the parser artifacts before cargo publish #267
Conversation
This file contains 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
|
Thanks! Appreciate your great work! |
dmfay
reviewed
Jul 30, 2024
DerekStride
force-pushed
the
fix-publish-workflow
branch
from
8eb8308 to
66e754e
Compare
dmfay
approved these changes
Jul 31, 2024
matthias-Q
approved these changes
Aug 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
The cargo publish workflow failed because the parser files weren't present. By running
npm ciwe force the files to be generated and ensure the test suite passes before publishing the crate.https://github.com/DerekStride/tree-sitter-sql/actions/runs/10167937438/job/28121386966
Note
In the meantime I've published v0.3.3 manually: https://crates.io/crates/tree-sitter-sequel