Uh oh!
There was an error while loading. Please reload this page.
ci(release): stop publishing to crates.io - #11
Conversation
The release workflow previously attempted to publish both the bus contract and the main crate to crates.io, but neither crate is actually published there — they are consumed as git submodules and the real artifact is the module bundle built later in the same job. The missing `CARGO_REGISTRY_TOKEN` caused these steps to fail, taking the entire release down with them and blocking the `native-bundles` job that depends on this workflow succeeding. The fix removes the `cargo publish` calls entirely and keeps only `cargo package` for the bus contract as a cheap manifest validation step, while dropping the packaging of the main crate because its path dependency on the bus contract makes it unpackageable without a registry lookup. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
Warning Review limit reachedYour included review limit has been reached. You’re in a promotional period — use the checkbox below to run this review for free:
On-demand reviews are free for the next 28 days. After that, they cost $0.25 per reviewed file. How can I continue?Run this review now using the option above, or comment You can also wait for the limit to reset (next review available in 11 minutes), then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
What
Removes the two
cargo publishsteps from the release workflow, and thecargo package --package tinydocsstep that cannot work without them.Why
The v0.1.14 release run (32628924101) failed at Package and publish the bus contract with:
Neither
tinydocsnortinydocs-busexists on crates.io, and neither is meant to: hosts consume this repository as a git submodule for the wire contract and load the module artifact this workflow builds.native-bundleshasneeds: publish, so a registry upload nobody reads was gating every module artifact in the release. Same conclusion tinywallet reached in tinyhumansai/tinywallet#25.cargo packagestays fortinydocs-bus— it is the cheap check that the manifest is packageable. It cannot stay fortinydocs, which depends ontinydocs-busby path: packaging rewrites a path dependency to a registry version and then looks it up, so it fails on a crate that by design will never be in the index.Verification
Re-cutting the release after this merges is the check.