Update the pinned tinybus submodule to latest - #3
Conversation
Update the pinned commit for the tinybus vendored dependency to incorporate upstream fixes or improvements. 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 30 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 49 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 |
What changed and why
Moves the
vendor/tinybusgitlink from0b161d2toc35105f(tinyhumansai/tinybus#15, "attest-pinned-release"). Gitlink only — no source
changes in this repository, per the vendored-dependency rule in
AGENTS.md.Upstream brings roughly 5k lines across 28 files: a new
secretmodule, a newstreammodule with base64 framing, substantial work inmodule/host.rsandrouter.rs, and newdocs/modules/coverage forattest,secret, andstream.Public API and behavior changes
None. The template's own surface is untouched, and nothing upstream required an
adaptation on this side.
Validation
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo build --all-targets --all-featurescargo test --all-featuresRUSTDOCFLAGS="-D warnings" cargo doc --no-deps --all-featurescargo deny check allcargo build --locked --release --lib -p templatecargo run -p template --example verify_module -- target/release/libtemplate.soGreetCargo.lockis unchanged: the tinybus crates keep version0.1.0and theirdependency set did not move.
The two tinybus surfaces the release workflow calls were checked explicitly
rather than assumed, since neither is exercised by CI:
crates/tinybus/examples/github_module_host.rsstill exists.tinybus modules checksum --path ... --output ...still accepts the sameflags (verified by running
--helpagainst the new pin).Follow-up, not in this change
Upstream added an
attestmodule and documentation for attesting a pinnedrelease. This repository's release workflow does not use it. Adopting it is a
deliberate change to the release contract and belongs in its own PR.