You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(modules): reconcile six module pins with their releases - #8534
check-module-pins fails on main for six modules: the registry record (the runtime artifact) names one release, while the gitlink (the contract this build compiles against) sits a few commits past an older tag. #8530 recorded this ("check-module-pins | fails: 6 ids") and left it. This PR reconciles all six by moving both pins to the module's next release, which contains the current gitlink. Nothing moves backwards.
Module
Registry
Gitlink (before)
Gitlink (after)
tinysearch
0.5.4 → 0.5.5
96d6922 (v0.5.2-25)
927c656 (v0.5.5)
tinydocs
0.2.7 → 0.2.8
14f8240 (v0.2.4-85)
c387488 (v0.2.8)
tinyvoice
0.4.2 → 0.4.3
85ce603 (v0.4.1-5)
172f019 (v0.4.3)
tinymcp
0.20.5 → 0.20.6
d42d345 (v0.20.3-4)
e098e53 (v0.20.6)
tinyconnectors
0.22.1 → 0.22.2
e66c8d3 (v0.22.0-4)
6a3eec0 (v0.22.2)
tinyhosts
0.4.5 → 0.4.6
8d210af (v0.4.2-15)
fd30e46 (v0.4.6)
For each module:
the new tag is the only tag that contains the old gitlink;
it's the latest tag on that module's main, and the new gitlink is on main;
the old gitlink is an ancestor of the new one, so this only moves forward;
the GitHub release exists, is published (not a draft), and carries checksum.toml.
How
Same tooling as #8530: node scripts/modules/release-and-repin.mjs <id> --version X.Y.Z --yes for each module. It rewrites the record's version, release_url and every asset's archive/sha256 verbatim from the release's own checksum.toml, then checks out the tag in vendor/<id>. No digest was computed locally.
Other changes that come with the move:
Tests that pin a release (registry_release_manifest_tests.rs tinyvoice, registry_tests.rs tinymcp/tinysearch, documents_tests.rs, tests/agent_harness_e2e.rs): the expected archives and digests were taken independently from each release's checksum.toml, so they still cross-check the records. The CONTRACT_VERSION asserts are unchanged and still pass.
Cargo.lock and crates/openhuman-app/Cargo.lock follow the moved crates:
module versions bump;
tinydocs 0.2.8 drops some dependencies (pdfrs, syntect, the font-subsetting crates, calamine 0.37 → 0.38).
Public API / behavior
At runtime, hosts download and load the six new releases in place of the old ones. No source changes.
Validation (local)
Static lane, every step run as the lane runs it: all ok. That includes module-pins ("all pins accounted for", 14 records) and submodule-monotonic ("6 submodule pin(s) moved forward").
storage-bypass needs full history; it passed after unshallowing.
cargo check --locked -p openhuman --all-targets: ok.
cargo check --locked -p openhuman-modules-linked --all-targets --features all: ok.
cargo tree --locked for crates/openhuman-app: ok after the lock update.
cargo test -p openhuman --lib --features <product> -- modules::registry modules::documents: 35 passed, 3 failed, none from this PR:
contract_tests::a_product_feature_build_carries_all_thirteen_records and every_record_matches_its_contract_constants fail identically on main. With all product features registry::ALL has 14 records, but the tests expect 13 and the contract table lists 13. This PR doesn't change ALL.
documents::held_outputs_are_released_after_success_read_failure_and_cancellation needs the tinydocs native module staged (install-test-modules.sh), which this machine doesn't have.
Summary by CodeRabbit
Module Updates
Updated TinyDocs to 0.2.8, TinyHosts to 0.4.6, TinyMCP to 0.20.6, TinyConnectors to 0.22.2, TinySearch to 0.5.5, and TinyVoice to 0.4.3.
Updated the available release packages across supported platforms.
Updated the pinned commits for all seventeen vendored tiny* submodules to their current upstream revisions.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
…nystoragedrivers
Update the vendored submodule pointers to their latest revisions. The tinysecurity and tinystoragedrivers checkouts are recorded as dirty, so their working trees carry uncommitted changes that should be committed upstream before the next bump.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Updated the pinned commits for the vendored tiny* submodules to pick up their latest upstream changes.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the pinned versions and checksums for the tinydocs, tinysearch, tinyvoice, and MCP connector modules to their latest releases so the registry resolves the current artifacts.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the tinyhosts module record to version 0.4.6, refreshing the release URL and the archive names and SHA-256 checksums for every platform asset. The vendored tinyconnectors submodule is advanced to the matching revision.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
…rates
Bumped calamine to 0.38.0 and moved ppt-rs to a newer revision, which removes several now-unneeded transitive dependencies such as bincode, bzip2, pdfrs, and the duplicate kurbo 0.13.1. The lockfile shrinks accordingly with no change to the project's own code.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Bump the pinned tinyvoice version and refresh every platform artifact filename and digest so the release manifest test matches the 0.4.3 build.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the pinned module versions and their published release manifests to the latest releases, refreshing the asset filenames and checksums for tinymcp 0.20.6 and the documents module 0.2.8 so the registry tests match what was actually published.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Updated the locked versions of the tinyconnectors, tinydocs, tinyhosts, tinymcp, and tinysearch bus crates to their latest patch releases.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Update the tinyhosts pin test to 0.4.6 or core tests fail
Verdict: Ready for maintainer review · Priority: none Coverage: Reviewed 10 of 18 files; not reviewed: Cargo.lock, crates/openhuman…, and 6 additional unreviewed files.
Diagnostics and supporting details
Full summary
Pull request purpose (title): chore(modules): reconcile six module pins with their releases. Purpose (title): chore(modules): reconcile six module pins with their releases. The pull request fixes the six `check-module-pins` failures recorded in #8530 by moving both the registry record and the vendor gitlink forward to each module's next release: tinysearch 0.5.4→0.5.5, tinydocs 0.2.7→0.2.8, tinyvoice 0.4.2→0.4.3, tinymcp 0.20.5→0.20.6, tinyconnectors 0.22.1→0.22.2, and tinyhosts 0.4.5→0.4.6. For each module the record's version, release_url and every asset archive/sha256 are rewritten from the published release's checksum.toml, and the pinning tests follow. At runtime hosts download and load the six new module releases in place of the old ones; no source behavior changes. The tests lane notes the new sha256 digests could not be verified against the published checksum.toml files (vendor submodules not checked out, no network), so digest correctness is unverified rather than confirmed. The commits lane notes one earlier finding still open. The latest-push-delta section is unavailable.
Unreviewed paths
Cargo.lock
crates/openhuman-app/Cargo.lock
vendor/tinyconnectors
vendor/tinydocs
vendor/tinyhosts
vendor/tinymcp
vendor/tinysearch
vendor/tinyvoice
Review snapshot
Change surface
Files
Review signal
Count
Production
5
Active findings
0
Tests
5
Noted findings
0
Documentation
0
Resolved findings
14
Configuration
0
Pending checks/questions
0
Completeness: Complete Test assessment: Test coverage is assessed from changed tests and lane evidence; execution is not claimed without trusted check data.
What changed
Six module registry records are re-pinned to new releases, with version, release_url, and every platform asset's archive name and sha256 digest replaced from each release's own checksum.toml: tinydocs 0.2.8, tinyhosts 0.4.6, tinymcp 0.20.6, tinyconnectors 0.22.2, tinysearch 0.5.5, and tinyvoice 0.4.3. The TinySearch record's source comment now cites the v0.5.5 checksum file. The vendor gitlinks for the six modules and the two Cargo.lock files follow the moved crates, though those paths are not in the reviewed diff. Net runtime effect is that hosts fetch and load the six new module releases instead of the old ones.
Features
Modified — tinydocs record re-pinned to 0.2.8: The registry record now names tinydocs 0.2.8 with the v0.2.8 release URL and per-platform archive names/digests taken from that release's checksum.toml, so hosts fetch the newer docs/wallet module artifact. (crates/openhuman-core/src/modules/registry/records_docs_wallet.rspub(crate) const TINYDOCS: ModuleRecord = ModuleRecord {)
Modified — tinyhosts record re-pinned to 0.4.6: The registry record now names tinyhosts 0.4.6 with the v0.4.6 release URL and re-derived archive/digest values for every host key, so hosts download and load the newer hosting module instead of 0.4.5. (crates/openhuman-core/src/modules/registry/records_extra.rspub(crate) const TINYHOSTS: ModuleRecord = ModuleRecord {)
Modified — tinymcp record re-pinned to 0.20.6: The MCP module record points at the v0.20.6 release with a full new digest/archive set, changing which MCP client artifact is downloaded and loaded at runtime. (crates/openhuman-core/src/modules/registry/records_mcp_connectors.rspub(crate) const TINYMCP: ModuleRecord = ModuleRecord {)
Modified — tinyconnectors record re-pinned to 0.22.2: The connectors record points at v0.22.2 with refreshed archives and digests, so the OAuth connector module loaded by hosts moves to the newer release. (crates/openhuman-core/src/modules/registry/records_mcp_connectors.rspub(crate) const TINYCONNECTORS: ModuleRecord = ModuleRecord {)
Modified — tinysearch record re-pinned to 0.5.5: The search record names 0.5.5 with new per-platform archives and digests, and its checksum provenance comment now cites the published v0.5.5 checksum.toml; hosts fetch the newer search module. (crates/openhuman-core/src/modules/registry/records_search.rspub(crate) const TINYSEARCH: ModuleRecord = ModuleRecord {)
Modified — tinyvoice record re-pinned to 0.4.3: The voice record names 0.4.3 with refreshed archives and digests from the published release, changing the voice module artifact hosts load. (crates/openhuman-core/src/modules/registry/records_voice.rspub(crate) const TINYVOICE: ModuleRecord = ModuleRecord {)
Tests
modification — The tinyhosts pin test now asserts record.version == "0.4.6", that all 17 assets use the `tinyhosts-0.4.6-` archive prefix with 64-char digests, and the new ubuntu-24.04-x86_64 digest, matching the re-pinned record.: Exact-value assertions that would fail on a stale pin; the tests lane reports the earlier tinyhosts pin mismatch is resolved by this change. (crates/openhuman-core/src/hosting/hosting_tests.rsfn tool_declarations_match_the_released_module_contract() {)
modification — The tinyvoice release-manifest test pins version 0.4.3 and the full per-platform archive/digest table for the new release, cross-checking the record against independently taken checksum values.: Exact-value comparisons that would fail on a stale pin; digest correctness against the published checksum.toml is unverified per the tests lane. (crates/openhuman-core/src/modules/registry_release_manifest_tests.rsfn tinychannels_registry_matches_scoped_runtime_release() {)
modification — The tinymcp registry test is renamed to the v0206 manifest and asserts version 0.20.6, the v0.20.6 release URL, and the full new archive/digest table.: Exact-value comparisons that would fail on a stale pin; digest correctness against the published checksum.toml is unverified per the tests lane. (crates/openhuman-core/src/modules/registry_tests.rsfn tinymcp_registry_matches_the_published_v0205_release_manifest() {)
modification — The tinysearch registry test asserts version 0.5.5 and the new ubuntu-24.04-x86_64 digest alongside the unchanged bus name, object path and contract version.: Exact-value comparisons that would fail on a stale pin; digest correctness against the published checksum.toml is unverified per the tests lane. (crates/openhuman-core/src/modules/registry_tests.rsfn tinysearch_registry_matches_bus_contract_and_published_release() {)
modification — The tinydocs documents test now asserts the pinned module version is 0.2.8 while still checking intake availability without loading.: Exact-value assertion that would fail on a stale pin. (crates/openhuman-core/src/modules/documents_tests.rsfn every_member_this_client_calls_is_one_the_contract_declares() {)
Positive: The critique lane answered with no findings and confirms the previously raised TinyHosts pin mismatch is fixed: the test now pins 0.4.6 consistently with the registry record, and the change introduces no new defect.
Lane summary: Reviewed 10 files; 0 findings. _The code index is behind this pull request (indexed at `f91de139f13c`), so retrieved context may be out of date._
security
Conclusion: Success
Scope reviewed: all assigned evidence
Positive: The security lane answered with no findings and confirms the earlier test-failure concern is resolved and nothing else in this file is affected.
Lane summary: Reviewed 10 files; 0 findings. _The code index is behind this pull request (indexed at `f91de139f13c`), so retrieved context may be out of date._
tests
Conclusion: Success
Scope reviewed: all assigned evidence
Positive: The tests lane answered with no findings: the prior tinyhosts finding is resolved, the re-pin is mirrored in each pinning test, and the assertions are exact-value comparisons that would fail on a stale pin. It notes the new sha256 digests could not be verified against the published checksum.toml files, so digest correctness is unverified rather than confirmed.
Lane summary: The prior finding is resolved: `hosting_tests.rs` now asserts `record.version == "0.4.6"` and the `tinyhosts-0.4.6-` archive prefix, matching the registry record, so the test no longer fails against the new pin. The rest of the diff is a mechanical version/digest re-pin across six module records, each mirrored in its pinning test (tinyvoice, tinymcp, tinysearch, tinydocs, tinyhosts) plus the e2e version assertions; the assertions are exact-value comparisons that would fail on a stale pin, so they earn their keep. I could not verify the new sha256 digests against the published `checksum.toml` files (the vendor submodules are not checked out and there is no network access here), so digest correctness is unverified rather than confirmed. _The code index is behind this pull request (indexed at `f91de139f13c`), so retrieved context may be out of date._
commits
Conclusion: Success
Scope reviewed: all assigned evidence
Positive: The commits lane answered with no sensitive content in committed files, noting one earlier finding still open.
Lane summary: No sensitive content in committed files. (1 earlier finding(s) still open) _The code index is behind this pull request (indexed at `f91de139f13c`), so retrieved context may be out of date._
description
Conclusion: Success
Scope reviewed: all assigned evidence
Positive: It could not verify the committed Cargo.lock changes or vendor gitlinks, which do not appear in the diff.
Lane summary: The description matches the diff: all six registry records and their release URLs move to the new versions, the assets and digests are rewritten, and the pin assertions in tests follow. The earlier disputed finding about the tinyhosts pin test is now fixed by this diff (`assert_eq!(record.version, "0.4.6")` and the new ubuntu-24.04-x86_64 digest in `hosting_tests.rs`), so it is dropped. I could not verify the committed Cargo.lock changes or the vendor gitlinks, since neither appears in the diff. _The code index is behind this pull request (indexed at `f91de139f13c`), so retrieved context may be out of date._
The reason will be displayed to describe this comment to others. Learn more.
Requesting changes: 2 lane(s) blocking, worst finding is high.
Fix or reply to the findings below and push. The next review clears this automatically once they are gone — you should not need to dismiss anything by hand.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The registry bump leaves a non-ignored hosting test pinned to 0.4.5, causing it to fail when the hosting feature is enabled until its version, archive prefix, and digest expectations are updated to 0.4.6.
Bump the pinned module version, archive prefix, and ubuntu-24.04-x86_64 checksum in the registry test so it matches the newly released tinyhosts 0.4.6 artifact set.
Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
The reason will be displayed to describe this comment to others. Learn more.
Refresh the hosting test's TinyHosts release expectations
With the hosting feature enabled, as it is in the shipped product feature set, hosting::test::the_module_registry_pins_the_released_hosts_artifact_set still expects version 0.4.5, the tinyhosts-0.4.5- archive prefix, and the old Ubuntu digest in crates/openhuman-core/src/hosting/hosting_tests.rs:188-195. This registry bump makes that previously passing test fail immediately in the product unit suite run by scripts/test-rust-with-mock.sh:371-373. Update all three expectations alongside the other release-pinning tests.
crates/openhuman-app/Cargo.lock is excluded by !**/*.lock
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
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: 07b95aae-8fde-49c5-8f53-e3d54e96834e
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
Trigger review
Walkthrough
Six module registry entries now reference newer releases, with updated release URLs, archive names, and checksums. Related tests expect the new versions and asset metadata. Six vendor subproject references point to updated commits.
Changes: Module release pin updates
Layer / File(s)
Summary
Registry release records crates/openhuman-core/src/modules/registry/records_docs_wallet.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/records_search.rs, crates/openhuman-core/src/modules/registry/records_voice.rs
Registry records for TinyDocs, TinyHosts, TinyMCP, TinyConnectors, TinySearch, and TinyVoice now reference newer versions. Their release URLs, archive names, and checksums are updated.
Release test expectations crates/openhuman-core/src/hosting/hosting_tests.rs, crates/openhuman-core/src/modules/documents_tests.rs, crates/openhuman-core/src/modules/registry_release_manifest_tests.rs, crates/openhuman-core/src/modules/registry_tests.rs, tests/agent_harness_e2e.rs
Tests now expect the updated versions and relevant archive names and checksums. The TinyMCP Arch ARM64 archive expectation uses the archlinux stem.
tinyhumansai/openhuman#7335 — The issue covers registry pins, gitlinks, and published module releases; this PR updates those records and references.
tinyhumansai/openhuman#8056 — The issue assigns ownership of registry pins and digests; this PR updates release records, checksums, and gitlinks.
tinyhumansai/openhuman#7455 — The issue identifies pin consistency, including TinyVoice and TinyMCP; this PR updates their release records and vendor references.
tinyhumansai/openhuman#7343 — The issue concerns stale module pins and artifacts; this PR updates six modules’ release records, checksums, and vendor references.
Possibly related PRs
tinyhumansai/openhuman#8412 — Updates the same six module pins in registry records, tests, and vendor references.
tinyhumansai/openhuman#8409 — Updates TinyHosts and TinyMCP pins in registry records, tests, and vendor references.
tinyhumansai/openhuman#8530 — Updates the TinySearch vendor reference that this PR advances, along with its registry record and tests.
Suggested reviewers:m3ga-mind
Merge Risk: Minimal · previous review 59bb3
The release pins and associated expectations advance together, with no demonstrated merge-blocking defect. TinySearch compatibility remains unverified rather than known to be broken.
Pre-merge checks: 4 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Docstring Coverage
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks: 4 passed
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title "chore(modules): reconcile six module pins with their releases" matches the main change. The PR moves the registry records, test pins, and vendored submodule gitlinks for six modules (tinyse…
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: Title check
Explanation
The title "chore(modules): reconcile six module pins with their releases" matches the main change. The PR moves the registry records, test pins, and vendored submodule gitlinks for six modules (tinysearch, tinydocs, tinyvoice, tinymcp, tinyconnectors, tinyhosts) to their new releases. The title is specific about the scope (six module pins) and the purpose (aligning them with releases). It does not name each module, but that detail is not required.
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 with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 10 files. (6 skipped: 6 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 version line, And sniffs each checksum, neat and fine. Six pins hop forward, fresh and bright, New archives settle into sight. The test suite nods, the burrow’s right.
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
The reason will be displayed to describe this comment to others. Learn more.
The previously-blocking findings are resolved. Clearing the changes request.
Diagnostics
Total spend: $0.0074
tinysweeperBot
added
priority: p3
Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.
and removed
priority: p1
Next. Wrong behaviour a user will hit, or a security weakness behind a condition.
labels
Nov 3, 2026
The reason will be displayed to describe this comment to others. Learn more.
Additional comments: 1
vendor/tinysearch-1-1: 1
1-1: Minor · Potential issue · Heavy lift
Unverified finding
We couldn't verify this from the code. It is shown for review, not as a verified issue.
The updated tinysearch source may change its host-facing contract without a matching host adaptation; the supplied context does not show the new commit’s interface or every host entry point.
Module initialization or a search request could fail despite the gitlink and registry pin advancing together.
This can occur when: A host builds and loads tinysearch from the new vendored commit using an unchanged entry point or data format.
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: 2e582b6b-7e78-42cd-a36b-06664b76f143
Commits
Reviewing files that changed from the base of the PR and between ed6970e and 59bb33e.
Files ignored due to path filters: 2
Cargo.lock is excluded by !**/*.lock
crates/openhuman-app/Cargo.lock is excluded by !**/*.lock
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
priority: p3Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![tinysweeper[bot]](https://avatars.githubusercontent.com/in/4526585?s=60&v=4){kind=small}
tinysweeper
Bot
added
the
priority: p1
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
check-module-pinsfails onmainfor six modules: the registry record (the runtime artifact) names one release, while the gitlink (the contract this build compiles against) sits a few commits past an older tag. #8530 recorded this ("check-module-pins| fails: 6 ids") and left it. This PR reconciles all six by moving both pins to the module's next release, which contains the current gitlink. Nothing moves backwards.v0.5.2-25)v0.5.5)v0.2.4-85)v0.2.8)v0.4.1-5)v0.4.3)v0.20.3-4)v0.20.6)v0.22.0-4)v0.22.2)v0.4.2-15)v0.4.6)For each module:
main, and the new gitlink is onmain;checksum.toml.How
Same tooling as #8530:
node scripts/modules/release-and-repin.mjs <id> --version X.Y.Z --yesfor each module. It rewrites the record'sversion,release_urland every asset'sarchive/sha256verbatim from the release's ownchecksum.toml, then checks out the tag invendor/<id>. No digest was computed locally.Other changes that come with the move:
registry_release_manifest_tests.rstinyvoice,registry_tests.rstinymcp/tinysearch,documents_tests.rs,tests/agent_harness_e2e.rs): the expected archives and digests were taken independently from each release'schecksum.toml, so they still cross-check the records. TheCONTRACT_VERSIONasserts are unchanged and still pass.Cargo.lockandcrates/openhuman-app/Cargo.lockfollow the moved crates:Public API / behavior
At runtime, hosts download and load the six new releases in place of the old ones. No source changes.
Validation (local)
module-pins("all pins accounted for", 14 records) andsubmodule-monotonic("6 submodule pin(s) moved forward").storage-bypassneeds full history; it passed after unshallowing.cargo check --locked -p openhuman --all-targets: ok.cargo check --locked -p openhuman-modules-linked --all-targets --features all: ok.cargo tree --lockedforcrates/openhuman-app: ok after the lock update.cargo test -p openhuman --lib --features <product> -- modules::registry modules::documents: 35 passed, 3 failed, none from this PR:contract_tests::a_product_feature_build_carries_all_thirteen_recordsandevery_record_matches_its_contract_constantsfail identically onmain. With all product featuresregistry::ALLhas 14 records, but the tests expect 13 and the contract table lists 13. This PR doesn't changeALL.documents::held_outputs_are_released_after_success_read_failure_and_cancellationneeds the tinydocs native module staged (install-test-modules.sh), which this machine doesn't have.Summary by CodeRabbit