Skip to content

chore(modules): pin TinyBox v0.2.2, TinyHosts v0.4.4, TinyMCP v0.20.3 - #8409

Merged
M3gA-Mind merged 2 commits into
tinyhumansai:mainfrom
M3gA-Mind:chore/bump-tinybox-tinyhosts-tinymcp-2026-10-26
Oct 26, 2026
Merged

M3gA-Mind merged 2 commits into
tinyhumansai:mainfrom
M3gA-Mind:chore/bump-tinybox-tinyhosts-tinymcp-2026-10-26

Conversation

@M3gA-Mind

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

Copy link
Copy Markdown
Collaborator

Summary

Moves three loadable modules to their 2026-10-24 releases. For each one this moves the registry record, the vendor/ gitlink, the tests that hard-code its release, and both lockfiles.

module from to gitlink
tinybox v0.2.1 v0.2.2 9b06976300
tinyhosts v0.4.3 v0.4.4 88aef248d4
tinymcp v0.20.2 v0.20.3 50c0390096

How each module is moved

  • Records: digests come from the GitHub release asset digests and are checked against each release's checksum.toml. All 51 match. Each release ships the same 17 archives as the one before it.
  • Tests: the test digests also come from the release, not copied from the record. The changed tests are the TinyBox and TinyMCP release-manifest tests in registry_tests.rs, the TinyHosts artifact-set test in hosting_tests.rs, and TinyBox's ignored pinned-loader test.
  • Gitlinks: each gitlink moves to its release tag's commit.
  • Old references: none are left outside vendor/ and the lockfiles, whether versions or digests. .github pins none of these three modules.

Host contract

  • TinyBox v0.2.2: 410 commits, 49 files. The bus contract goes from 2.0 to 2.1, which only adds the resource-aware jailed exec member StartJailedExecWithResources (with NativeJailRequest). The 2.0 request shapes are unchanged. Nothing in the host breaks:
    • The new Error::EgressRollbackFailed variant affects nothing, since no host code matches on that error type exhaustively.
    • The egress allowlist now refuses loopback entries, and the host doesn't use EgressAllowlist.
    • Nothing changes in storage collections, grants, storage_callback or the wire format.
  • TinyHosts v0.4.4: version-only. Its tinytools requirement moves from 0.5 to 0.6, so the [patch] that redirects it to the vendored tinytools 0.6.0 now matches its version requirement.
  • TinyMCP v0.20.3: version-only, and the contract stays (1, 28).
  • tinybus: all three release locks resolve tinybus 0.1.6, the host's series, so the loader accepts them.

Lockfiles

Both lockfiles were regenerated with targeted cargo update -p on a remote host, then composed so that every changed line comes from these bumps:

  • the path-crate versions;
  • the tinybox-bus 0.2.2 references;
  • tinybox-docker's new ipnet, sha2 and tempfile edges.

The regen also re-pointed Windows-only windows-sys/windows-core edges and re-resolved tempfile's getrandom edge. These lines are kept as on main.

The app lock also catches up tinychannels-bus 0.1.43 and tinyflows 0.9.2. Main's app lock is behind on these, and the same regen on plain main produces exactly these two lines.

Checks

Checked on a remote host at 6530aed, whose parent is main e8707ea:

  • cargo metadata --locked: passes for the root and app locks, and leaves the tree clean (no lock rewrite).
  • cargo test -p openhuman --lib (core features):
    • 24/24 modules::registry tests pass. That includes tinybox_registry_matches_the_published_v022_release_manifest, tinymcp_registry_matches_the_published_v0203_release_manifest and the release-manifest file.
    • every_row_has_a_valid_generated_grant passes.
  • Full lanes against main e8707ea: no new failure.
    • The coverage lane has the same 8 failing tests by name on main and here.
    • the_module_registry_pins_the_released_hosts_artifact_set passes with full features.
    • static:rust-fmt (crates/openhuman-embed/src/lib.rs:252,261) and static:agent-runtime-boundary fail on main too.
  • Main has since moved to 0caf743. That merges cleanly with this branch; its only lock change is tinyliveagents.

Summary by CodeRabbit

  • Updates
    • Updated TinyBox to version 0.2.2, TinyHosts to 0.4.4, and TinyMCP to 0.20.3.
    • Refreshed the available platform-specific builds for all three modules. Existing platform support remains unchanged.

Records, release-manifest tests and gitlinks move to each release tag.
Digests come from the GitHub asset digests, checked against every
release's checksum.toml. TinyBox's bus contract moves 2.0 -> 2.1, which
only adds the resource-aware jailed exec member; TinyHosts and TinyMCP
are version-only.
Composed from a regenerated lock: path-crate versions, the tinybox-bus
0.2.2 references, and tinybox-docker's new ipnet, sha2 and tempfile
edges. Windows edge re-points and the getrandom re-resolution are left
as on main. The app lock also catches up tinychannels-bus 0.1.43 and
tinyflows 0.9.2, which main's app lock had left behind.
@tinysweeper

tinysweeper Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Reviewed head: 6530aeda1d4e2a29588f7a585e47219659b60cb9

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 5 of 10 files; not reviewed: Cargo.lock, crates/openhuman…, and 3 additional unreviewed files.
Pull request purpose (title): chore(modules): pin…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore(modules): pin TinyBox v0.2.2, TinyHosts v0.4.4, TinyMCP v0.20.3. This pull request, titled "chore(modules): pin TinyBox v0.2.2, TinyHosts v0.4.4, TinyMCP v0.20.3", bumps three loadable modules to their 2026-10-24 releases by re-pinning the registry records (version, release URL, every platform archive name and sha256 digest), updating the vendor gitlinks and both lockfiles per the description, and updating the tests that hard-code each release. The review evidence covers 5 changed files; the pull-request description additionally lists Cargo.lock, crates/openhuman-app/Cargo.lock, and the three vendor gitlinks, which do not appear in the visible diff. The latest-push delta is unavailable, so no push-delta comparison is claimed.

Unreviewed paths

  • Cargo.lock
  • crates/openhuman-app/Cargo.lock
  • vendor/tinybox
  • vendor/tinyhosts
  • vendor/tinymcp

Review snapshot

Change surface Files Review signal Count
Production 2 Active findings 0
Tests 3 Noted findings 0
Documentation 0 Resolved findings 0
Configuration 0 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

Registry records for TinyBox, TinyHosts, and TinyMCP now point at versions 0.2.2, 0.4.4, and 0.20.3 respectively, with matching release URLs and refreshed per-platform archive names and digests across all 17 assets each. The registry, hosting, and TinyBox operations tests are updated to the new versions and digests, and the TinyBox bus contract assertion moves from (2, 0) to (2, 1). Per the description, vendor gitlinks for the three modules and both lockfiles are also moved, though those hunks are not present in the supplied diff.

Features

  • Modified — TinyBox registry record pinned to v0.2.2: TinyBox resolves to the 0.2.2 release, with all 17 platform archive names and sha256 digests replaced and the release URL updated, so deployments fetch the new artifacts. (crates/openhuman-core/src/modules/registry/records_extra.rs pub(crate) const TINYBOX: ModuleRecord = ModuleRecord {)
  • Modified — TinyHosts registry record pinned to v0.4.4: TinyHosts resolves to the 0.4.4 release with refreshed archive names, digests, and release URL; per the description this is a version-only release whose tinytools requirement moves to 0.6, matching the existing vendored-tinytools patch. (crates/openhuman-core/src/modules/registry/records_extra.rs pub(crate) const TINYHOSTS: ModuleRecord = ModuleRecord {)
  • Modified — TinyMCP registry record pinned to v0.20.3: TinyMCP resolves to the 0.20.3 release with refreshed archive names, digests, and release URL; its bus contract stays at (1, 28) per the unchanged assertion. (crates/openhuman-core/src/modules/registry/records_mcp_connectors.rs pub(crate) const TINYMCP: ModuleRecord = ModuleRecord {)

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

No active actionable findings.

Before merge

None.

How this fits together

flowchart LR
  n0["...ations_match_the_released_module_contract<br/>changed"]:::changed
  n1["...tches_the_published_v021_release_manifest<br/>changed"]:::changed
  n2["...ches_the_published_v0202_release_manifest<br/>changed"]:::changed
  n3["...tches_the_verified_v0260_release_manifest<br/>changed"]:::changed
  n4["..._local_grants_from_pinned_tinybox_release<br/>changed"]:::changed
  n5["config_with"]:::impacted
  n6["expect"]:::impacted
  n7["assert"]:::impacted
  n8["...ader_serves_the_published_tinybox_release"]:::impacted
  n9["...viders_and_confidential_local_preparation"]:::impacted
  n10["mock_client_with_docker_control_delay"]:::impacted
  n0 -->|calls| n5
  n0 -->|tests| n5
  n0 -->|calls| n6
  n1 -->|calls| n6
  n2 -->|calls| n6
  n3 -->|calls| n6
  n4 -->|calls| n6
  n4 -->|calls| n7
  n8 -->|calls| n6
  n8 -->|calls| n7
  n9 -->|calls| n5
  n9 -->|tests| n5
  n9 -->|calls| n6
  n10 -->|calls| n6
  classDef changed fill:#0d4429,stroke:#238636,color:#e6edf3
  classDef impacted fill:#161b22,stroke:#6e7681,color:#c9d1d9
  classDef flagged fill:#5a1e02,stroke:#d93f0b,color:#ffffff
  classDef blocking fill:#67060c,stroke:#f85149,color:#ffffff
Loading
Agent review details

critique

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: Reviewed 5 files; 0 findings. _The code index is behind this pull request (indexed at `c434a3d8acde`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: Reviewed 5 files; 0 findings. _The code index is behind this pull request (indexed at `c434a3d8acde`), so retrieved context may be out of date._

tests

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: This is a mechanical re-pin of three module releases (tinybox 0.2.1→0.2.2, tinyhosts 0.4.3→0.4.4, tinymcp 0.20.2→0.20.3) in the registry records, with the existing registry-manifest tests updated to the new versions and digests. The tests already pin version, release URL, every platform archive name and digest, and the tinybox contract version, so a regression here fails loudly. No behavioural defect found in the diff; the one thing I could not verify is that the digests were copied verbatim from each release's checksum.toml rather than recomputed locally, since the vendor submodules and published assets are not available to me. _The code index is behind this pull request (indexed at `c434a3d8acde`), so retrieved context may be out of date._

commits

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: Commits lane reports no sensitive content in committed files.
  • Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `c434a3d8acde`), so retrieved context may be out of date._

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: The description matches the diff: version strings, release URLs, archives and digests are bumped for tinybox, tinyhosts and tinymcp in both the registry records and the tests that mirror them, and the TinyBox contract assertion is moved to (2, 1) as the body states. No `.github`, lockfile or `vendor/` changes are shown in this diff despite the body claiming them, so I could not verify those claims, but nothing in the visible hunks contradicts the text and no line introduces a defect I can name. _The code index is behind this pull request (indexed at `c434a3d8acde`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.000880
  • Tokens: 577890 input · 6659 output · 124928 cached · 1901 embedding
  • Updated: 2026-10-26T08:42:16Z
Head State Pass summary
6530aeda1d4e ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-10-26T08:42:16Z)

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-26T08:45:20.313495Z 6530aed 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
Contributor

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: 631d7252-7b0e-4d99-a5fc-c59e71c60223
Commits

Reviewing files that changed from the base of the PR and between 0caf743 and 6530aed.

Files ignored due to path filters: 2
  • Cargo.lock is excluded by !**/*.lock
  • crates/openhuman-app/Cargo.lock is excluded by !**/*.lock
Files selected for processing: 8
  • crates/openhuman-core/src/hosting/hosting_tests.rs
  • crates/openhuman-core/src/modules/registry/records_extra.rs
  • crates/openhuman-core/src/modules/registry/records_mcp_connectors.rs
  • crates/openhuman-core/src/modules/registry_tests.rs
  • crates/openhuman-core/src/modules/tinybox/operations_tests.rs
  • vendor/tinybox
  • vendor/tinyhosts
  • vendor/tinymcp

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Walkthrough

The registry records and release-pinned tests now reference TinyBox 0.2.2, TinyHosts 0.4.4, and TinyMCP 0.20.3. The vendor references were also updated for all three modules. TinyBox’s expected contract version changed to 2.1.

Changes: Module release updates

Layer / File(s) Summary
TinyBox 0.2.2 release
crates/openhuman-core/src/modules/registry/records_extra.rs, crates/openhuman-core/src/modules/registry_tests.rs, crates/openhuman-core/src/modules/tinybox/operations_tests.rs, vendor/tinybox
The registry record and pinned-release tests now use version 0.2.2 and contract version 2.1. The 17 platform asset names and checksums were updated, along with the vendor reference.
TinyHosts 0.4.4 release
crates/openhuman-core/src/modules/registry/records_extra.rs, crates/openhuman-core/src/hosting/hosting_tests.rs, vendor/tinyhosts
The registry record and hosting test now use version 0.4.4. The platform asset names and checksums, pinned Ubuntu asset hash, and vendor reference were updated.
TinyMCP 0.20.3 release
crates/openhuman-core/src/modules/registry/records_mcp_connectors.rs, crates/openhuman-core/src/modules/registry_tests.rs, vendor/tinymcp
The registry record and release tests now use version 0.20.3. The 17 platform asset names and checksums, including the Arch Linux archive names, and the vendor reference were updated.

Priority: Low

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

Change: Other

Possibly related issues

  • tinyhumansai/openhuman#8369: This PR updates registry entries and tests for new TinyBox, TinyHosts, and TinyMCP releases and their checksums, matching the issue’s module-release adoption objective.

Possibly related PRs

Suggested reviewers: senamakel

Merge Risk: Minimal · up to 6530a

The release pins and test expectations appear aligned. No actionable merge-blocking issue is identified; complete the normal release checks before merging.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 5 files. (3 skipped: 3 … Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed Passed checks: 4 passed
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 main change: pinning the TinyBox, TinyHosts, and TinyMCP modules to their updated versions.
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

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 5 files. (3 skipped: 3 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

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

A rabbit checks each checksum line,
Three fresh releases now align.
New archive names hop into place,
TinyBox’s contract keeps its pace.
The vendor pins move on in time.

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

@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 9d5d30f into tinyhumansai:main Oct 26, 2026
31 of 33 checks passed
M3gA-Mind added a commit to senamakel/openhuman that referenced this pull request Oct 26, 2026
Conflicts were tinyhumansai#8409's TinyBox v0.2.2 / TinyHosts v0.4.4 / TinyMCP v0.20.3
pins against this branch's newer v0.2.3 / v0.4.5 / v0.20.4: records,
hosting_tests, registry_tests and the three gitlinks keep this branch's
side. vendor/tinyagents takes main's v3.1.1 (2b234b7) here; the next
commits move it to v3.1.2. Both lockfiles keep this branch's side and are
regenerated at the end of the series.
M3gA-Mind added a commit to senamakel/openhuman that referenced this pull request Oct 26, 2026
…d releases

operations_tests still asserted TinyBox 0.2.2 (main's tinyhumansai#8409 pin) against
the v0.2.3 record. The TinyWallet record comment names v0.27.0, and the
linked-modules manifest comment now says module repos require tinybus 0.3
(>=0.3.6).
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