Skip to content

chore(deps): pin tinystoragedrivers at its tinybus 0.3.6 commit - #182

Merged
M3gA-Mind merged 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:fix/tinybus-036-single-series
Oct 26, 2026
Merged

M3gA-Mind merged 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:fix/tinybus-036-single-series

Conversation

@M3gA-Mind

@M3gA-Mind M3gA-Mind commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

tinyflows main locks two tinybus series. The module uses 0.3.6 (6ce06bc). tinystoragedrivers 2.1.1 at bf1f0a9 pins tinybus 0.1.6 (0de2d28) for tinystoragedrivers-bus and -busproxy, and tinyflows-storage pins tinybus-sdk to the same 0.1.6 rev so that Connection stays one type with busproxy. openhuman's loader accepts only modules built in the host's tinybus series, so the module release has to resolve a single tinybus.

tinystoragedrivers#87 (merge 29471a1) moves that pin to tinybus 0.3.6 at 6ce06bc. No other tinystoragedrivers manifest changes between bf1f0a9 and 29471a1.

Changes

  • Every tinystoragedrivers dependency moves from bf1f0a9 to 29471a1 (adaptive, drivers, module, storage).
  • The tinyflows-storage tinybus-sdk dev-dependency moves from 0de2d28 to 6ce06bc.
  • Cargo.lock: the 11 tinystoragedrivers sources move to the new rev, and the tinybus 0.1.6 package is removed. All five tinybus 0.1.6 / tinybus 0.3.6 references become a single tinybus.
  • Nothing is orphaned: each dependency of the removed 0.1.6 package is still used by another package in the lock.

CI's cargo check --locked checks the lock edit.

Summary by CodeRabbit

  • Chores
    • Updated the underlying storage and messaging integrations to newer revisions. No user-facing behavior changes are noted.

tinystoragedrivers 2.1.1 at bf1f0a9 pinned tinybus 0.1.6 (git 0de2d28), so
the lock carried two tinybus series: 0.3.6 for the module and 0.1.6 for the
storage bus and busproxy. tinystoragedrivers#87 (29471a1) moves that pin to
tinybus 0.3.6 at 6ce06bc, the rev this workspace already patches crates-io to.

Pin every tinystoragedrivers crate at 29471a1 and the tinyflows-storage
`tinybus-sdk` test dependency at 6ce06bc, so the lock resolves one tinybus.
@tinysweeper

tinysweeper Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Reviewed head: 4cd72d4002ead2aea3d9826112a8aa8da6e383aa

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 4 of 5 files; not reviewed: Cargo.lock.
Pull request purpose (title): chore(deps): pin tin…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore(deps): pin tinystoragedrivers at its tinybus 0.3.6 commit. This pull request realigns tinyflows' dependency pins so the module release resolves a single tinybus series. Per the title and description, tinyflows main locked two tinybus series: the module uses tinybus 0.3.6 at 6ce06bc, while tinystoragedrivers 2.1.1 at bf1f0a9 pinned tinybus 0.1.6 at 0de2d28 for tinystoragedrivers-bus and -busproxy, and tinyflows-storage's tinybus-sdk dev-dependency was pinned to the same 0.1.6 rev to keep Connection one type with busproxy. Because openhuman's loader accepts only modules built in the host's tinybus series, the module release has to resolve one tinybus. The change moves every tinystoragedrivers dependency from bf1f0a9 to 29471a1 (the merge of tinystoragedrivers#87, which moves that pin to tinybus 0.3.6 at 6ce06bc), moves the tinyflows-storage tinybus-sdk dev-dependency from 0de2d28 to 6ce06bc, and, per the description, updates Cargo.lock so the 11 tinystoragedrivers sources move to the new rev, the tinybus 0.1.6 package is removed, and the five tinybus 0.1.6 / 0.3.6 references become a single tinybus, with no dependency orphaned. The description lane notes Cargo.lock was not shown in the diff despite the body's lock claims about an 11-source move and removal of the tinybus 0.1.6 package, so those claims could not be verified.

Unreviewed paths

  • Cargo.lock

Review snapshot

Change surface Files Review signal Count
Production 0 Active findings 0
Tests 0 Noted findings 0
Documentation 0 Resolved findings 0
Configuration 4 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 diff bumps git revision pins across four workspace manifests: crates/tinyflows-adaptive/Cargo.toml, crates/tinyflows-drivers/Cargo.toml, crates/tinyflows-module/Cargo.toml and crates/tinyflows-storage/Cargo.toml. tinystoragedrivers-api, tinystoragedrivers-types, tinystoragedrivers-testkit and tinystoragedrivers-busproxy references move from rev bf1f0a97fbe6165a6edd9521659c7f6859700761 to rev 29471a164619bcec03e5858a7d7ee0c65f52bf22 while keeping version 2.1.1. In crates/tinyflows-storage/Cargo.toml the tinybus-sdk dev-dependency (package tinybus) moves from rev 0de2d283f35cbbff08efad6fbe05537ffb74611b to rev 6ce06bc674e4f4d718aa51e643ef62c1f372e270. The pull request description also states Cargo.lock changes (11 tinystoragedrivers sources move, the tinybus 0.1.6 package is removed, the five tinybus references collapse to one, and nothing is orphaned), but Cargo.lock is not present in the supplied diff evidence, so those lock edits are described rather than observed here. No source code is changed.

Features

  • Modified — tinystoragedrivers revision pin moved to the tinybus 0.3.6 commit: All tinystoragedrivers dependencies in the workspace are pinned to rev 29471a164619bcec03e5858a7d7ee0c65f52bf22 instead of bf1f0a97fbe6165a6edd9521659c7f6859700761, keeping version 2.1.1. Per the description this is the merge of tinystoragedrivers#87, which moves tinystoragedrivers' own tinybus pin to 0.3.6 at 6ce06bc; the effect is that tinyflows' tinystoragedrivers stack no longer drags in the tinybus 0.1.6 series, so the module can resolve a single tinybus as the host loader requires. The dependency site in crates/tinyflows-drivers/Cargo.toml also adds an optional uuid workspace dependency and a store feature, and crates/tinyflows-module/Cargo.toml declares crate-type ["rlib", "cdylib"] and a static-link feature, while crates/tinyflows-storage/Cargo.toml sets publish = false and an ulid dependency; these are manifest-level entries matching the pinned revision bump rather than behavioural changes to runtime code. (crates/tinyflows-adaptive/Cargo.toml tinyflows = { path = "../tinyflows", features = ["store", "mock"] }, crates/tinyflows-drivers/Cargo.toml uuid = { workspace = true, optional = true }, crates/tinyflows-drivers/Cargo.toml store = [, crates/tinyflows-module/Cargo.toml crate-type = ["rlib", "cdylib"], crates/tinyflows-module/Cargo.toml static-link = [], crates/tinyflows-storage/Cargo.toml publish = false, crates/tinyflows-storage/Cargo.toml ulid = "1", crates/tinyflows-adaptive/Cargo.toml thiserror = "2")
  • Modified — tinyflows-storage tinybus-sdk dev-dependency moved to the host tinybus rev: The tinybus-sdk dev-dependency in crates/tinyflows-storage/Cargo.toml, which points at the tinybus package, moves from rev 0de2d283f35cbbff08efad6fbe05537ffb74611b to rev 6ce06bc674e4f4d718aa51e643ef62c1f372e270. The manifest comment requires this to stay on the rev tinystoragedrivers pins so tinybus::Connection is one type with its busproxy; the security lane states the tinybus bump matches the rev the root Cargo.toml already pins, keeping tinybus::Connection one type with its busproxy as the comment requires. Together with the tinystoragedrivers bump this is what collapses the two tinybus series onto one. (crates/tinyflows-storage/Cargo.toml publish = false, crates/tinyflows-storage/Cargo.toml ulid = "1")

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: Reviewed 2 files; 0 findings. 3 file(s) are the mechanical rename `bf1f0a97fbe6165a6edd9521659c7f6859700761` → `29471a164619bcec03e5858a7d7ee0c65f52bf22`, verified line for line; one of them was read to judge the substitution itself, the rest were not sent to a model. _The code index is behind this pull request (indexed at `bfccd0bf041d`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: The security lane was answered and reported no findings. It states the diff only bumps pinned git revisions for tinystoragedrivers (2.1.1, bf1f0a97 to 29471a16) and tinybus (0de2d283 to 6ce06bc6) in the storage manifest, that both packages are unpublished host-facing crates so the change does not reach the crates.io guard, that no vendored source under vendor/ was shown affected, and that the tinybus bump matches the rev the root Cargo.toml already pins, keeping tinybus::Connection one type with its busproxy as the comment requires. It records it could not inspect the tinystoragedrivers commit contents, but judged a revision bump with an identical version constraint and no code change not a reportable defect on this evidence.
  • Lane summary: The diff only bumps the pinned git revisions for tinystoragedrivers (2.1.1, bf1f0a97 → 29471a16) and tinybus (0de2d283 → 6ce06bc6) in tinyflows-storage's manifest. Both packages are unpublished host-facing crates, so the change does not reach the crates.io guard, no vendored source under vendor/ was shown to be affected, and the tinybus bump matches the rev the root Cargo.toml already pins — keeping `tinybus::Connection` one type with its busproxy, as the comment requires. I could not inspect the tinystoragedrivers commit contents, but a revision bump with an identical version constraint and no code change is not a reportable defect on this evidence. 3 file(s) are the mechanical rename `bf1f0a97fbe6165a6edd9521659c7f6859700761` → `29471a164619bcec03e5858a7d7ee0c65f52bf22`, verified line for line; one of them was read to judge the substitution itself, the rest were not sent to a model. _The code index is behind this pull request (indexed at `bfccd0bf041d`), 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 commits lane was answered and reported that no sensitive content is present in committed files, with 0 pending checks.
  • Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `bfccd0bf041d`), so retrieved context may be out of date._

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: It notes Cargo.lock was not shown in the diff despite the body claiming an 11-source move and removal of the tinybus 0.1.6 package, so that claim could not be verified, but nothing in the manifests contradicts the description.
  • Lane summary: The diff is a pure dependency-pin bump: every tinystoragedrivers reference moves from bf1f0a9 to 29471a1 and the tinyflows-storage tinybus-sdk dev-dependency moves from 0de2d28 to 6ce06bc, exactly as the description states. I was not shown Cargo.lock (it is absent from the diff despite the body claiming an 11-source move and removal of the tinybus 0.1.6 package), so I cannot verify that claim, but nothing in the manifests contradicts the description and I found no defect worth reporting. _The code index is behind this pull request (indexed at `bfccd0bf041d`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.001424
  • Tokens: 178777 input · 5409 output · 52736 cached · 243 embedding
  • Updated: 2026-10-26T08:57:53Z
Head State Pass summary
4cd72d4002ea ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-10-26T08:57:53Z)

tinysweeper 0.1.2

@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: 9aeb2741-61ca-4213-acb3-01e7a5cf5a54
Commits

Reviewing files that changed from the base of the PR and between 128d0f3 and 4cd72d4.

Files ignored due to path filters: 1
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing: 4
  • crates/tinyflows-adaptive/Cargo.toml
  • crates/tinyflows-drivers/Cargo.toml
  • crates/tinyflows-module/Cargo.toml
  • crates/tinyflows-storage/Cargo.toml

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

Four crate manifests update pinned Git revisions for tinystoragedrivers dependencies. The storage manifest also updates the tinybus-sdk revision. Dependency versions and feature declarations remain unchanged.

Changes: Dependency revision alignment

Layer / File(s) Summary
Update dependency pins
crates/tinyflows-adaptive/Cargo.toml, crates/tinyflows-drivers/Cargo.toml, crates/tinyflows-module/Cargo.toml, crates/tinyflows-storage/Cargo.toml
The manifests pin tinystoragedrivers dependencies to revision 29471a164619bcec03e5858a7d7ee0c65f52bf22. The storage manifest also pins tinybus-sdk to revision 6ce06bc674e4f4d718aa51e643ef62c1f372e270.

Priority: Normal

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

Change: Other

Possibly related issues

  • tinyhumansai/openhuman#8131 — The issue identifies this tinystoragedrivers pin correction as a remaining close condition, while covering broader restructuring beyond this PR.

Possibly related PRs

  • tinyhumansai/tinyflows#180 — This PR continues the dependency alignment by updating the tinystoragedrivers pin and the storage tinybus-sdk pin.

Suggested reviewers: senamakel

Merge Risk: Minimal · up to 4cd72

The pin updates are consistent with the stated goal of using one tinybus series and present no actionable merge risk.

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 describes the dependency pinning changes to tinystoragedrivers and the tinybus 0.3.6 commit.
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. (4 skipped: 4 unsupported.)

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

A rabbit checks each revision in a row,
New pins take root where Cargo winds blow.
The storage crate gets a tinybus tune,
Four manifests align beneath the moon.
I nibble the diff, then hop away.

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

@tinysweeper tinysweeper Bot added the priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect. label Oct 26, 2026
@M3gA-Mind
M3gA-Mind merged commit 8845f46 into tinyhumansai:main Oct 26, 2026
9 checks passed
@M3gA-Mind
M3gA-Mind deleted the fix/tinybus-036-single-series branch October 26, 2026 12:19
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