[senamakel]

Bumps nested vendor/tinybus to v0.3.6 (6ce06bc), widens the tinybus/tinybus-module requirement to >=0.3.6, <0.4, and repins tinytools to v0.6.0 (41cc80a). No code changes needed. clippy -D warnings, rustdoc -D warnings, fmt, nextest (240) and doc tests pass locally.

Summary by CodeRabbit

• Chores
  • Updated underlying components to newer revisions.

[tinysweeper]

Tiny Sweeper review

Reviewed head: 036a95336038a8e088349ac9e61c2f1b5d30deae

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

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore: bump tinybus to v0.3.6, tinytools to v0.6.0. This pull request, titled "chore: bump tinybus to v0.3.6, tinytools to v0.6.0," raises the tinybus and tinybus-module version requirement from the 0.1 series to >=0.3.6, <0.4 and repins tinytools to a newer upstream revision (41cc80a), alongside a Cargo.lock update and a vendor/tinybus submodule bump. The critique and description lanes answered and noted the manifest changes match the stated intent, with the critique lane flagging that tinybus 0.3.6 API compatibility was unverified.

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

Cargo.toml bumps tinybus and tinybus-module from >=0.1.3, <0.2 to >=0.3.6, <0.4 (both caret-style bounds, default-features off, macros and modules features retained on tinybus), and repins tinytools from rev 3a01641 to 41cc80a. Cargo.lock and the vendor/tinybus gitlink are updated to match.

Features

• Modified — tinybus dependency requirement widened to >=0.3.6, <0.4: Resolves against the 0.3.6 release line instead of the 0.1 series; the features "macros" and "modules" with default-features=false are preserved. (Cargo.toml percent-encoding = { version = "2", optional = true })
• Modified — tinybus-module requirement widened to >=0.3.6, <0.4: Module-side SDK aligned to the same 0.3.6 release line as tinybus. (Cargo.toml)
• Modified — tinytools repinned to rev 41cc80ac: The git-pinned optional dependency now points at the newer upstream revision; the comment describing the single-package pin and tinytools::ToolResult typing remains applicable. (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
• Positive: Bounds remain caret-style ranges and the comment blocks above each entry still describe why the crate is needed.
• Lane summary: The diff bumps the tinybus/tinybus-module pin from the 0.1 series to >=0.3.6, <0.4 and moves the tinytools git rev. Both ranges are caret-style bounds and the tinytools comment block above the entry remains accurate for a git-pinned dependency. I could not verify the API compatibility of tinybus 0.3.6 (vendor/tinybus is not checked out and crate docs were not available), so whether `module_export_optional_static!`, `serve_at`, and the module types still exist with the same shape under 0.3.6 is unconfirmed; the author should confirm the vendored submodule gitlink is bumped to the matching TinyBus revision in the same change.

security

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: No untrusted-input, auth, network or permission change is introduced in the manifest; features stay minimal.
• Lane summary: The change only bumps version bounds and a pinned revision for three dependencies (tinybus, tinybus-module, tinytools). Bounds are caret-style ranges, features stay minimal and the existing comments still describe why each crate is needed; the tinytools revision is a pin to an upstream commit the repository already relies on. I cannot verify from the tree what changed in the upstream tinybus or tinytools revisions, so supply-chain contents of those commits are unchecked, but nothing in the manifest itself introduces an untrusted-input, auth, network or permission change.

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: Commits lane answered and reported no sensitive content in committed files.
• Lane summary: No sensitive content in committed files.

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: Description lane answered, stating the diff matches the description exactly and requires no code changes.
• Lane summary: The diff widens the tinybus/tinybus-module version requirement and repins tinytools to a newer revision, matching the description exactly; no code changes, so nothing to check against the lookup rules. Description is accurate and sufficient.

Evidence and run details

• Models: ladder/vectors-oai3, deepseek-v4.1-flash
• Spend: $0.000168
• Tokens: 148918 input · 2903 output · 64512 cached · 114 embedding
• Updated: 2026-10-26T06:24:09Z

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

[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	✅ Completed 2026-10-26T06:25:44.816981Z	036a953	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: 67759376-9029-438b-a371-6d09dac720a1

Commits

Reviewing files that changed from the base of the PR and between 88aef24 and 036a953.

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 pull request updates the optional TinyBus version ranges and vendored submodule reference. It also changes the pinned Git revision for the optional tinytools dependency.

Changes: Dependency updates

Layer / File(s)	Summary
Update dependency references Cargo.toml, vendor/tinybus	The optional tinybus and tinybus-module version ranges now accept >=0.3.6, <0.4. The TinyBus submodule reference and the optional tinytools Git revision also changed.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related issues

• tinyhumansai/openintents-core#202 — The issue describes planned tinycomputer integration involving tinybus; this pull request updates TinyBus dependency compatibility.

Possibly related PRs

• tinyhumansai/tinyhosts#39 — Both PRs update the optional tinytools dependency pin.
• tinyhumansai/tinyhosts#42 — Both PRs update the vendor/tinybus submodule reference and its version requirements.

Suggested reviewers: m3ga-mind, tinysweeper

Merge Risk: Minimal · up to 036a9

The dependency ranges and vendored revisions are aligned with the stated update, with no actionable merge-blocking risk identified.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title accurately summarizes the dependency updates: tinybus moves to v0.3.6 and tinytools is updated to the v0.6.0 revision.
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 version range,
TinyBus hops to commits new.
Tinytools finds a pinned revision,
The manifest records each change.
Then off I go, with ears held high!}

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

[tinysweeper]

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0002