Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
let's give this a try when you're ready (of course, as |
|
Idea: bump the language crate to (If it's good enough for Apple...) |
|
And then we can't patch it without breaking the coupling. :^) |
|
Why would we need to patch it? AFAIUI, the crate is a simple "gear shift" layer, and bumps are needed if and only if the library is bumped. |
40f147d to
249df00
Compare
|
Opted to leave the language crate at 0.1.6. Bumping to 0.1.26 could help clear things up for us short term, but would ultimately be more confusing if/when the language crate gets bumped out of the normal release cycle again. |
It looks like the last publish workflow failed because the
tree-sitter-languagecrate already had version0.1.5published (likely directly via crates.io) before other changes went into it in this repo. Bumping the language crate's version to0.1.6should allow publishing to succeed, which will then in turn allow the rest of the repo to go through its publishing motions.Leaving this as a draft for now, to be picked up tomorrow.