[senamakel]

Bumps vendor/tinybus to v0.3.6 (6ce06bc) and widens the tinybus/tinybus-module requirement to >=0.3.6, <0.4; Cargo.lock refreshed. No code changes needed. fmt, clippy -D warnings, rustdoc -D warnings, nextest (220) and doc tests pass locally.

Summary by CodeRabbit

• Chores
  • Updated the versions of supporting components used by the application.
  • Existing feature selection remains unchanged, and this update does not change the application's user-facing features or behavior.

[tinysweeper]

Tiny Sweeper review

Reviewed head: 9e47aa4e281e7ce5051c35ed942a5d02084b203b

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 nested t…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore: bump nested tinybus to v0.3.6. The pull request is titled "chore: bump nested tinybus to v0.3.6" and described as bumping vendor/tinybus to v0.3.6 (6ce06bc), widening the tinybus/tinybus-module requirement to >=0.3.6, <0.4, refreshing Cargo.lock, with no code changes needed.

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 now requires tinybus with version >=0.3.6, <0.4 (keeping default-features = false and the macros and modules features) and tinybus-module with version >=0.3.6, <0.4, replacing the prior >=0.1.3, <0.2 requirements. Per the pull-request description, the vendor/tinybus submodule is bumped to v0.3.6 (6ce06bc) and Cargo.lock is refreshed, with no code changes needed. The critique lane notes the workspace consumers use workspace = true and the [patch.crates-io] entries still point at the pinned submodule, so the ranges only matter for standalone crates.io resolution.

Features

• Modified — tinybus workspace dependency requirement: Widens the required tinybus version range from >=0.1.3, <0.2 to >=0.3.6, <0.4 while retaining default-features = false and the macros and modules features; the change only affects resolution outside the pinned submodule patch. (Cargo.toml, Cargo.toml tinysearch-bus = { path = "crates/tinysearch-bus" })
• Modified — tinybus-module workspace dependency requirement: Widens the required tinybus-module version range from >=0.1.3, <0.2 to >=0.3.6, <0.4 for the module-side SDK. (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: The critique lane answered with no findings; it noted the ranges only matter for standalone crates.io resolution since consumers use workspace = true and patch entries still point at the pinned submodule, with nothing in the diff showing a break.
• Lane summary: The change bumps the `tinybus` and `tinybus-module` version ranges to `>=0.3.6, <0.4`; both consumers use `workspace = true`, and the `[patch.crates-io]` entries still point at the pinned submodule, so the ranges only matter for standalone crates.io resolution. I could not verify that `0.3.6` exposes the `test-support` feature and the `test_support` module the e2e tests use, or that the submodule's crate versions satisfy the new constraint, because `vendor/tinybus` was not readable here — but nothing in the diff shows a break, so I have no findings.

security

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The security lane answered with no findings, noting the change only bumps version requirements and introduces no new code paths, network calls, deserialization or secrets.
• Lane summary: The change only bumps the version requirements for the `tinybus` and `tinybus-module` workspace dependencies from `0.1.x` to `0.3.x`; it introduces no new code paths, network calls, deserialization, or secrets. The repository rule to keep `vendor/tinybus` pinned as a submodule and change its source in its own repository is not violated by a version requirement edit in `Cargo.toml`, and no concrete misbehaviour is visible in this file.

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 commits lane answered with no findings, reporting no sensitive content in committed files.
• Lane summary: No sensitive content in committed files.

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The description lane answered with no findings, finding the description accurately matches the version-range widening and the mechanical Cargo.lock refresh.
• Lane summary: The diff widens the tinybus and tinybus-module requirements to >=0.3.6, <0.4 and is described accurately, including the Cargo.lock refresh, which is the mechanical consequence of a submodule bump. The description matches what the diff does; no defects found in the change itself.

Evidence and run details

• Models: ladder/vectors-oai3, deepseek-v4.1-flash
• Spend: $0.000147
• Tokens: 114747 input · 3055 output · 41472 cached · 41 embedding
• Updated: 2026-10-26T06:23:53Z

Head	State	Pass summary
9e47aa4e281e	ready for maintainer review	0 active finding(s), 0 resolved finding(s) (at 2026-10-26T06:23:53Z)

[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:24:44.434304Z	9e47aa4	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: 38a1e3c0-32a0-4170-8309-086594fc761a

Commits

Reviewing files that changed from the base of the PR and between 22c22d2 and 9e47aa4.

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 now accepts tinybus and tinybus-module versions from 0.3.6 to below 0.4. The vendor/tinybus submodule reference also points to a new commit. The tinybus feature selection is unchanged.

Changes: Tinybus dependency update

Layer / File(s)	Summary
Update tinybus dependency source and constraints Cargo.toml, vendor/tinybus	The workspace dependency ranges now target versions from 0.3.6 to below 0.4. The vendor/tinybus submodule reference changed to commit 6ce06bc674e4f4d718aa51e643ef62c1f372e270. The tinybus feature selection is unchanged.

Priority: Low

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

Change: Other

Possibly related PRs

• tinyhumansai/tinysearch#33: It updated the same submodule pointer to the commit that this change replaces.

Suggested reviewers: m3ga-mind

Merge Risk: Minimal · up to 9e47a

The dependency update has no identified merge-blocking risk; the checked-in resolution is consistent with the new constraints.

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 describes the primary change: updating the vendored tinybus dependency to v0.3.6.
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,
Then hops to a newer bus.
The module follows close behind,
The feature flags stay as they were,
And tiny paws approve the change.}

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

[tinysweeper]

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0001