Skip to content

chore(deps): take tinystoragedrivers v0.10.0 by range, tinybus main - #81

Merged
senamakel merged 1 commit into
mainfrom
tsd-0.10
Oct 14, 2026
Merged

senamakel merged 1 commit into
mainfrom
tsd-0.10

Conversation

@senamakel

@senamakel senamakel commented Oct 14, 2026 •

Copy link
Copy Markdown
Member

Part of tinyhumansai/openhuman#7610 and #7543.

OpenHuman's vendored TinyAgents now carries tinystoragedrivers v0.10.0, and a module linked beside the host must resolve the same storage crates (a root [patch] replaces a git dependency only when its version requirement admits the patched crate). This crate named v0.8.0 by exact version.

  • Takes tinystoragedrivers at tag v0.10.0 for standalone builds, and names versioned dependencies by the range >=0.8.0, <1 so a host that patches in its own copy is admitted without another module release for every storage bump.
  • Bumps the nested vendor/tinybus to tinybus main (1f33d1b): the v0.10.0 tinystoragedrivers-busproxy uses Connection::accept_stream_from / emit_to, which tinybus gained after 0.1.5.
  • Patch version bump so the change can be released and re-pinned.

Verified locally: cargo build --workspace --all-features, cargo test --workspace --all-features and cargo clippy --workspace --all-targets -D warnings are clean, with no source changes.

Summary by CodeRabbit

  • Chores
    • Updated the release version and refreshed bundled components to align with this release. These changes update the software package without adding user-facing features or changing documented functionality. No changes to public capabilities are included in this update.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 14, 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-14T01:29:13.412625Z 1be9beb 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 14, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c8e54248-4dcd-45ca-8dd0-5efc09317644
📥 Commits

Reviewing files that changed from the base of the PR and between e75d42e and 1be9beb.

⛔ 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 package version changes to 0.1.32. The storage-driver dependency requirements and Git tag are updated. The tinybus submodule points to a new commit.

Changes: Release and dependency updates

Layer / File(s) Summary
Workspace and vendored dependency updates
Cargo.toml, vendor/tinybus
The workspace and tinybox-drivers versions change to 0.1.32. Three storage-driver dependencies use tag v0.10.0 and accept versions >=0.8.0, <1. The tinybus submodule reference changes to commit 1f33d1be1901a2d44bfe674cd7cf294cf384882.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 1be9b

The dependency update has no identified issue requiring a change before merge.

### Architecture Summary

Architecture risk: 🔵 Low · up to 1be9b

The change affects 1 system.

Changed systems: Cargo.toml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — Cargo.toml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in Cargo.toml: The workspace package version changes from 0.1.31 to 0.1.32.
  • observed — Modified behavior in Cargo.toml: The three tinystoragedrivers dependencies change from exact 0.8.0 requirements at Git tag v0.8.0 to the range >=0.8.0, <1 at tag v0.10.0. The tinybox-drivers path dependency version changes from 0.1.31 to 0.1.32.
  • observed — Modified behavior in vendor/tinybus: The vendor/tinybus submodule reference now points to commit 1f33d1be1901a2d44bfe674cd7cf294cf384882 instead of eb5cf727071a6eb12f9efa3db8ec59e54039f336.
Pre-merge checks: Passed 5
Passed Passed checks: 5 passed
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the main dependency updates: tinystoragedrivers v0.10.0 with a version range and the tinybus main revision.
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.
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

A rabbit checks the version line,
And sees the drivers’ range align.
A tiny bus hops to a new commit,
While manifest numbers neatly fit.
Then off through clover, quick and bright!

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

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1be9bebdab

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Cargo.toml
Comment thread vendor/tinybus
@senamakel
senamakel merged commit 7f74374 into main Oct 14, 2026
14 checks passed
@tinysweeper

tinysweeper Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Tiny Sweeper reviewed this change across 5 lane(s) and found 0 active actionable finding(s). Detailed lane evidence and any incomplete work are listed below.

State: Ready for maintainer review
Priority: none
Reviewed head: 1be9bebdab64
Updated: 2026-10-14T03:05:08Z

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.

Features

None identified with supported citations.

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: The change is a mechanical version bump (workspace 0.1.31 → 0.1.32, matching `tinybox-drivers` constraint) plus a move of the three tinystoragedrivers ports from tag v0.8.0 to v0.10.0; the committed Cargo.lock already resolves those crates at 0.10.0 from tag v0.10.0 with a single patched `tinybus`, so the manifests and lock agree and nothing here breaks the build. The one thing worth fixing before merge is that the port requirements were widened to `>=0.8.0, <1`, which is not the caret range the repository's dependency rule mandates and which silently accepts semver-incompatible 0.x releases. _The code index is behind this pull request (indexed at `2d5df3af5d3b`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: This change only bumps the workspace version to 0.1.32, updates the internal `tinybox-drivers` path-dependency version to match, and moves the three `tinystoragedrivers` git dependencies from tag v0.8.0 to v0.10.0 with a widened `>=0.8.0, <1` requirement. The lockfile already records the v0.10.0 commit, so versions stay consistent, and nothing security-relevant (input handling, auth, subprocess, CI permissions) is touched. No findings. _The code index is behind this pull request (indexed at `2d5df3af5d3b`), 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: Neutral
  • Scope reviewed: all assigned evidence
  • Lane summary: Nothing sensitive found in what this pull request commits.

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: The diff is a dependency-and-version-only change: it moves the workspace package version to 0.1.32, renames the three tinystoragedrivers git tag dependencies from v0.8.0 to v0.10.0 with the version range `>=0.8.0, <1`, and bumps the `tinybox-drivers` path dependency to 0.1.32. That matches the description, which explicitly frames this as taking tinystoragedrivers v0.10.0 by range with a patch version bump and no source changes. The `>=0.8.0, <1` requirement does admit v0.10.0, and Cargo.lock already pins all tinystoragedrivers crates at tag v0.10.0, so the manifest and lock stay consistent. The description does not mention the nested `vendor/tinybus` gitlink bump in the body's summary text beyond the bullet — actually it does state it explicitly — so nothing significant in the diff is undisclosed; the diff shown contains no submodule gitlink change to verify, but that is a description-to-diff coverage matter I cannot check further. No defect found in the described change. _The code index is behind this pull request (indexed at `2d5df3af5d3b`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.003317
  • Tokens: 131860 input · 44311 output · 13568 cached · 83 embedding
Head State Pass summary
1be9bebdab64 ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-10-14T03:05:08Z)

tinysweeper 0.1.2

@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.

             $0.0033 · 131,860 in / 44,311 out · 13,568 cached (10%) · ladder/vectors-oai3, deepseek-v4.1-flash · 83 embedded
critique:    $0.0019 · 59,964 in  / 25,365 out · 6,144 cached (10%)  · deepseek-v4.1-flash
security:    $0.0009 · 45,885 in  / 11,579 out · 5,632 cached (12%)  · deepseek-v4.1-flash
description: $0.0005 · 23,701 in  / 6,187 out  · 1,792 cached (8%)   · deepseek-v4.1-flash

@tinysweeper tinysweeper Bot added the priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect. label Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant