Skip to content

chore(deps): bump tinybus v0.3.6, tinytools v0.6.0, tinystoragedrivers v2.1.1 - #154

Merged
senamakel merged 4 commits into
mainfrom
bump-tinybus-0.3.6
Oct 26, 2026
Merged

senamakel merged 4 commits into
mainfrom
bump-tinybus-0.3.6

Conversation

@senamakel

@senamakel senamakel commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

Bumps nested vendor/tinybus to v0.3.6 (6ce06bc), widens tinybus/tinybus-module to >=0.3.6,<0.4, repins tinytools (41cc80a) and tinystoragedrivers v2.1.1 (bf1f0a9). No code changes needed. Clippy -D warnings, rustdoc -D warnings, fmt and scripts/test-features.sh pass locally.

Summary by CodeRabbit

  • Chores
    • Updated the versions of underlying components and refreshed related reference information. Existing feature selections and documented feature descriptions remain unchanged.
    • No new user-facing features or behavior changes are included in this update.

senamakel and others added 4 commits October 26, 2026 06:22
Update the vendored tinybus submodule to the latest upstream commit.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Raise the tinybus and tinybus-module version requirements from the 0.1.x range to >=0.3.6, <0.4 so the generated integration builds against the current frozen module ABI.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the tinystoragedrivers git dependencies to revision bf1f0a9, which
carries version 2.1.1. The lockfile also picks up the transitive getrandom
and sha2 versions that the new revision requires.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the reviewed canonical TinyTools commit referenced by the pure vocabulary spec to 41cc80a, keeping the pinned revision in sync with the current reviewed baseline.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
@tinysweeper

tinysweeper Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Reviewed head: 7cf3f6864689a74796066088323f1b7e8907f879

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 2 of 4 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 v0.3.6, tinytools v0.6.0, tinystoragedrivers v2.1.1. Dependency-pin bump with no source changes: tinybus and tinybus-module are widened to >=0.3.6,<0.4, tinytools is repinned to commit 41cc80a, and all tinystoragedrivers crates move together to v2.1.1 at rev bf1f0a9 in Cargo.toml. The spec doc is updated to match the new tinytools commit. The latest-push delta could not be computed, so this describes the whole pull request only.

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 1 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

- Root workspace manifest (Cargo.toml): tinybus relaxed from >=0.1.3,<0.2 to >=0.3.6,<0.4 while keeping default-features off and the macros/modules features; tinybus-module matches at >=0.3.6,<0.4. Existing explanatory comments above each entry are untouched. - Root workspace manifest (Cargo.toml): tinytools git pin moves from rev 1ec3468f6602b69b955a0e94105ed63abb5aa98c to rev 41cc80ac9acf37a14f20be94f60ee552749f1540. - Root workspace manifest (Cargo.toml): tinystoragedrivers-api, -types, -busproxy, -testkit, -document and -secrets all move from version 2.1.0 at rev 2856dfa to version 2.1.1 at rev bf1f0a9, with the document crate's memory-feature configuration unchanged. - docs/specs/pure-vocabulary.md: the reviewed TinyTools canonical commit reference is updated from 1ec3468 to 41cc80a so the spec matches the manifest pin. - The pull-request description also mentions Cargo.lock and the nested vendor/tinybus gitlink moving to v0.3.6; those files are outside the diff excerpt shown here.

Features

  • Modified — Pure-vocabulary spec commit reference updated: The specification's statement that generic lexical sanitization lives in TinyTools 0.6 now names commit 41cc80a, so the documented provenance matches the manifest pin and the pinned wire forms and registry identifiers remain pinned as stated. (docs/specs/pure-vocabulary.md persisted registry identifiers, declarations and error wire forms remain pinned)

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: Critique lane reviewed both changed files (2 of 2) and raised no findings.
  • Lane summary: Reviewed 2 files; 0 findings. _The code index is behind this pull request (indexed at `5f92b5f82f3a`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: The diff only bumps pinned dependency versions and revision hashes (tinybus/tinybus-module to 0.3.6, tinytools and tinystoragedrivers git revs) in the root workspace manifest; no untrusted input paths, permissions, or CI configuration change, and version bumps are consistent across all tinystoragedrivers entries. One repository rule requires a comment above each dependency entry, which these edits leave intact rather than remove. Nothing reportable. 1 file was not security-reviewed: docs/specs/pure-vocabulary.md (prose or tabular data). _The code index is behind this pull request (indexed at `5f92b5f82f3a`), 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: Commits lane reported no sensitive content in committed files.
  • Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `5f92b5f82f3a`), so retrieved context may be out of date._

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: Description lane judged the description consistent with the diff, including the tinytools hash change in the spec and the stated 'no code changes needed'.
  • Lane summary: The description matches the diff: it bumps tinybus to >=0.3.6,<0.4, repins tinytools to 41cc80a, updates tinystoragedrivers to v2.1.1 at bf1f0a9, and the docs change to the tinytools commit hash is the only other edit — all consistent with the stated "no code changes needed". I found nothing significant the description omits; the vendor/tinybus gitlink change it mentions is not visible in this diff excerpt but is not contradicted by it. _The code index is behind this pull request (indexed at `5f92b5f82f3a`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.000197
  • Tokens: 118112 input · 2615 output · 20480 cached · 276 embedding
  • Updated: 2026-10-26T06:25:33Z
Head State Pass summary
7cf3f6864689 ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-10-26T06:25:33Z)

tinysweeper 0.1.2

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

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:27:03.895379Z 7cf3f68 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

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

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: b7c71f51-4b27-48e9-b7b8-2586b9029d27
Commits

Reviewing files that changed from the base of the PR and between 50c0390 and 7cf3f68.

Files ignored due to path filters: 1
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing: 3
  • Cargo.toml
  • docs/specs/pure-vocabulary.md
  • 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

Dependency requirements and pinned revisions change for TinyBus, TinyTools, and TinyStorageDrivers. The TinyBus vendor reference and the documented TinyTools sanitizer commit also change.

Changes: Dependency Updates

Layer / File(s) Summary
TinyBus dependency and vendor reference
Cargo.toml, vendor/tinybus
The tinybus and tinybus-module version requirements change to >=0.3.6, <0.4. The vendor/tinybus submodule points to a new commit.
TinyTools and storage driver revisions
Cargo.toml, docs/specs/pure-vocabulary.md
The tinytools revision and all six tinystoragedrivers revisions change. The documented canonical TinyTools sanitizer commit changes to 41cc80a.

Priority: Low

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

Change: Other

Possibly related issues

  • The report of embedded TinyMCP startup and module-availability failures may relate to the updated TinyBus requirements. The available context does not establish that this change fixes the reported failures.

Possibly related PRs

  • tinyhumansai/tinymcp#150: This PR continues the TinyBus vendor update from the commit introduced in PR #150 and updates the matching dependency requirement.

Suggested reviewers: m3ga-mind

Merge Risk: Minimal · up to 7cf3f

No actionable merge-blocking risk is established by these dependency pin updates.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely identifies the dependency updates for TinyBus, TinyTools, and TinyStorageDrivers. It matches the main changes in the pull request.
Docstring Coverage Passed 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 Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed 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. (3 skipped: 3 unsupported.)

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

A rabbit checks the pins in place
TinyBus hops to a newer trace
TinyTools marks its commit clear
Storage drivers shift their gear
The vendor burrow welcomes change

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

@tinysweeper tinysweeper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0002

@senamakel
senamakel merged commit fe4681e into main Oct 26, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant