ci(release): publish loomweave-llm to crates.io before its dependents#83
Merged
Merged
Conversation
The crates.io publish-order list never included loomweave-llm (extracted from loomweave-core in 1.4.0), so `cargo publish -p loomweave-mcp` failed with "no matching package named loomweave-llm found" and left 1.4.0's crates.io publish partial (loomweave-llm/mcp/cli unpublished; PyPI + GitHub Release unaffected). Insert `publish loomweave-llm` right after loomweave-core — it has no internal loomweave deps and must precede loomweave-mcp and loomweave-cli, which both pin loomweave-llm==<version>. cargo publish is idempotent here (already-uploaded counts as success), so this is safe on the next tag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
db08949 to
b5d4a2c
Compare
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.
The crates.io publish-order list in
release.ymlnever includedloomweave-llm(extracted fromloomweave-corein 1.4.0). On the 1.4.0 tag,cargo publish -p loomweave-mcpfailed with "no matching package named loomweave-llm found" and halted — leavingloomweave-llm,loomweave-mcp,loomweave-cliunpublished on crates.io (PyPI + GitHub Release were unaffected).Insert
publish loomweave-llmright afterloomweave-core: it has no internal loomweave deps and must precedeloomweave-mcpandloomweave-cli, which both pinloomweave-llm==<version>.cargo publishis idempotent in this job (already-uploaded counts as success), so this is safe on the next tag.Prevents recurrence; the 1.4.0 crates.io publish itself is being completed out-of-band via local
cargo publish.🤖 Generated with Claude Code