fix(release): skip crates.io, use cargo-dist installers#53
Merged
Conversation
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
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.
Why
The crates.io publish failed because
tinycloud-node-server's path deps (e.g.tinycloud-auth) lack version specifiers. Publishing the binary requires publishing all internal workspace crates first. We're deferring that.Changes
release-plz.toml:publish = falsefortinycloud-node(stops the failed publish loop)Cargo.toml: enable cargo-dist shell + powershell installers, addworkspace.resolver = "2"to silence resolver warningResult
cargo install tinycloud-nodewon't work until we publish to crates.iocargo install --gitstill works (builds from source)Next step (separate one-off)
Reserve the
tinycloud-nodename on crates.io by publishing a minimal v0.0.1 placeholder from a temp dir.