[senamakel]

Bumps the nested vendor/tinybus submodule to v0.3.6 (6ce06bc), widens the tinybus/tinybus-module requirement to >=0.3.6,<0.4, pins tinystoragedrivers to v2.1.1 (bf1f0a9) and refreshes Cargo.lock.

No code changes were needed. Verified locally: clippy --workspace --all-targets --all-features -D warnings, rustdoc -D warnings, fmt, nextest (1350 passed), doc tests.

Co-authored-by: Medulla medulla@tinyhumans.ai

Summary by CodeRabbit

• Chores
  • Updated underlying components and compatibility requirements. No user-facing feature or behavior changes are included in this update. These maintenance changes do not alter the app’s visible functionality.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-26T06:24:08.417556Z	31ed7dc	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4610db6c-4774-452a-90ce-b4336f41132c

Commits

Reviewing files that changed from the base of the PR and between 9b06976 and 31ed7dc.

Files ignored due to path filters: 1

• Cargo.lock is excluded by !**/*.lock

Files selected for processing: 2

• Cargo.toml
• vendor/tinybus

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The workspace manifest updates the accepted versions and revisions for tinybus and tinystoragedrivers. The vendored tinybus submodule reference also changes.

Changes: Workspace dependency updates

Layer / File(s)	Summary
tinybus version and revision Cargo.toml, vendor/tinybus	The manifest accepts tinybus and tinybus-module versions >=0.3.6, <0.4. The vendored tinybus reference points to a new commit.
tinystoragedrivers versions Cargo.toml	All six tinystoragedrivers dependencies now use version 2.1.1 at revision bf1f0a97fbe6165a6edd9521659c7f6859700761.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related issues

• tinyhumansai/tinybox issue 27: The tinybus version and vendored revision changes affect the bus interface and versioning described in the issue.

Suggested reviewers: m3ga-mind

Merge Risk: Minimal · up to 31ed7

No actionable merge-blocking issue was found in these dependency updates.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely identifies the dependency updates for tinybus and tinystoragedrivers, which match the main changes in the pull request.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit checks the bus once more,
New tinybus versions reach the door.
Storage drivers join the line,
Revisions match and dependencies align.
The rabbit hops through fields of green,
With tidy manifests on the screen.}

_{Comment @coderabbitai help to get the list of available commands.}

[tinysweeper]

Tiny Sweeper review

Reviewed head: 31ed7dcbff6003eef82e9d68bd050d8cf34a623a

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 1 of 3 files; not reviewed: Cargo.lock, vendor/tinybus.
Pull request purpose (title): chore(deps): bump ti…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore(deps): bump tinybus to v0.3.6 and tinystoragedrivers to v2.1.1. This pull-request is titled "chore(deps): bump tinybus to v0.3.6 and tinystoragedrivers to v2.1.1" and described as bumping the nested vendor/tinybus submodule to v0.3.6, widening the tinybus/tinybus-module requirement to >=0.3.6,<0.4, pinning tinystoragedrivers to v2.1.1 (bf1f0a9), and refreshing Cargo.lock. The overall behavior is a dependency-only version bump of the workspace manifest: the tinybus and tinybus-module requirements move from the 0.1.x range to >=0.3.6,<0.4, and all six tinystoragedrivers entries move together from rev 05eaada with version 2.1.0 to rev bf1f0a9 with version 2.1.1. The critique lane (answered, 1/1 files covered) found no internal inconsistency in the diff, and the security lane (answered) saw no widened capabilities or new enabled features. The description lane (answered) judged the description accurate and the change safe to merge. The commits lane (answered) found no sensitive content in committed files. No findings were raised in any answered lane.

Unreviewed paths

• Cargo.lock
• vendor/tinybus

Review snapshot

Change surface	Files	Review signal	Count
Production	0	Active findings	0
Tests	0	Noted findings	0
Documentation	0	Resolved findings	0
Configuration	1	Pending checks/questions	0

Completeness: Complete
Test assessment: No supported feature-to-test mapping was available; this does not mean tests are absent or passed.

What changed

The workspace manifest (Cargo.toml) widens the tinybus dependency to the >=0.3.6,<0.4 range while keeping default-features disabled and the macros and modules features enabled, and widens tinybus-module to >=0.3.6,<0.4. All six tinystoragedrivers crates (types, api, busproxy, tinystoragedrivers itself, testkit, and document) move from version 2.1.0 at rev 05eaada to version 2.1.1 at rev bf1f0a9, consistently across every entry, with the default-features = false setting on the main crate preserved. No crate source or test files are modified. The pull-request also reports a vendor/tinybus submodule bump to v0.3.6 and a Cargo.lock refresh, which are not part of the supplied manifest excerpt.

Features

• Modified — tinybus workspace dependency bump to >=0.3.6,<0.4: Moves the bus dependency to the 0.3.x line while preserving default-features = false and the macros and modules features; this is a major-range jump from >=0.1.3,<0.2. (Cargo.toml)
• Modified — tinybus-module workspace dependency bump to >=0.3.6,<0.4: Moves the module-side SDK to the matching 0.3.x range so it stays aligned with tinybus. (Cargo.toml tinybox-docker = { path = "crates/tinybox-docker", version = "0.2.2" })
• Modified — tinystoragedrivers crates pin bump to v2.1.1 at rev bf1f0a9: All six tinystoragedrivers entries (types, api, busproxy, main crate, testkit, document) advance together from 2.1.0/05eaada to 2.1.1/bf1f0a9, keeping the rev consistent across the set and retaining default-features = false on the main crate. (Cargo.toml)

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

No active actionable findings.

Before merge

None.

Agent review details

critique

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Lane summary: This is a dependency-version bump in the workspace manifest: tinybus/tinybus-module move to the 0.3.x line and the tinystoragedrivers crates move to a new git rev at 2.1.1. The versions are caret-compatible and the rev is bumped consistently across all six TSD entries, so there is no internal inconsistency in the diff. I could not verify that the TinyBus 0.1.x → 0.3.x major jump leaves the API the module crates call unchanged, nor that Cargo.lock (not shown in this diff) is updated to match the new git rev — if the lockfile still pins the old rev, `cargo build --locked` fails. I have not raised either as a finding because no diff line proves it. _The code index is behind this pull request (indexed at `248ff4a07a71`), so retrieved context may be out of date._

security

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered security lane reported that both dependencies remain pinned to exact git revisions or caret-bounded ranges, no new features or crates are enabled, and no capabilities are widened.
• Lane summary: This bumps the pinned TinyBus/TinyBusModule range (0.1.3 → 0.3.6) and the tinystoragedrivers git rev/version (2.1.0 → 2.1.1) in the workspace manifest. Both remain pinned to exact git revisions or caret-bounded ranges, no new features or crates are enabled, and no capabilities are widened; nothing in this manifest change introduces a security defect I can see. _The code index is behind this pull request (indexed at `248ff4a07a71`), so retrieved context may be out of date._

tests

• Conclusion: Neutral
• Scope reviewed: all assigned evidence
• Lane summary: No behavioural change: nothing outside documentation, configuration and tests.

commits

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered commits lane reported no sensitive content in committed files covering its review.
• Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `248ff4a07a71`), so retrieved context may be out of date._

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered description lane found the description accurately describes the dependency bump and that nothing in the manifest change would break existing path patches.
• Lane summary: The diff is a dependency bump only: it widens the tinybus/tinybus-module workspace requirements to >=0.3.6,<0.4 and moves the tinystoragedrivers git crates from rev 05eaada to bf1f0a9 with version 2.1.1. The description accurately describes this, and no crate source or test file is touched, so no repository code rule applies here. The Cargo.lock refresh the body mentions is not visible in the excerpt I was given, but nothing in the workspace manifest changes in a way that would break the existing path patches. Safe to merge. _The code index is behind this pull request (indexed at `248ff4a07a71`), so retrieved context may be out of date._

Evidence and run details

• Models: ladder/vectors-oai3, deepseek-v4.1-flash
• Spend: $0.000180
• Tokens: 117284 input · 2972 output · 25600 cached · 142 embedding
• Updated: 2026-10-26T06:24:51Z

Head	State	Pass summary
31ed7dcbff60	ready for maintainer review	0 active finding(s), 0 resolved finding(s) (at 2026-10-26T06:24:51Z)

[tinysweeper]

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0002