Repository navigation
chore(vendor): bump tinyskills, tiny-artifacts and tinyhumans-sdk to their release tags - #8410
Conversation
…their release tags - tinyskills d74e9d5 -> v0.5.2 (d999239): tokio, tinystoragedrivers 2.1.1 and tinytools rev bumps; no API change. - tiny-artifacts 25a7cf9 -> v0.1.1 (b8920f7): tinytools and tinystoragedrivers rev bumps; no API change. - tinyhumans-sdk f42b128 -> rust-v0.2.1 (0652d2e): route metadata refresh, memory-admin and elevenlabs-webhook routes excluded from the OpenAPI sync, doc-link fixes; no API change. tinystoragedrivers is already pinned at bf1f0a9 (2.1.1), and both git dependencies resolve through the root patch tables.
…ans-sdk versions in Cargo.lock Only the four version lines change. A cargo update -p of these packages also re-targets unrelated windows-sys edges and downgrades tempfile's getrandom, which do not belong in a vendor bump.
Tiny Sweeper reviewReviewed head: Verdict: Ready for maintainer review · Priority: none Diagnostics and supporting detailsFull summaryPull request purpose (title): chore(vendor): bump tinyskills, tiny-artifacts and tinyhumans-sdk to their release tags. 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. Review snapshot
Completeness: Complete FeaturesNone identified with supported citations. TestsNo supported feature-to-test mapping was produced. Test execution is not inferred. FindingsNo active actionable findings. Before mergeNone. Agent review detailscritique
security
tests
commits
description
Evidence and run details
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
 |
| Layer / File(s) | Summary |
|---|---|
Update vendor references vendor/tiny-artifacts, vendor/tinyhumans-sdk, vendor/tinyskills |
Each vendor pointer now references a different commit. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Possibly related PRs
- tinyhumansai/openhuman#8325: Updated the same three vendor references to intermediate commits.
Suggested reviewers: senamakel
Merge Risk: 
7639d
-
The dependency updates introduce no established merge-blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly identifies the vendor dependency updates and names all three affected projects. It accurately describes the primary change. Docstring Coverage 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 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: 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 each vendor pin,
Three newer commits hop right in.
Tiny artifacts, skills, and SDK,
Now point to commits on their way.
The rabbit bounds along, content.
Comment @coderabbitai help to get the list of available commands.
![tinysweeper[bot]](https://avatars.githubusercontent.com/in/4526585?s=60&v=4){kind=small}
tinysweeper
Bot
added
the
priority: p3
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7639df4323
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
crates/openhuman-app/Cargo.lock records the same vendored path packages as the root lock, so it needs the same version-only update (tiny-artifacts 0.1.1, tinyhumans-sdk 0.2.1, tinyskills/tinyskills-drivers 0.5.2).
The desktop lock had also fallen behind the vendored tinychannels-bus (0.1.43) and tinyflows (0.9.2) path packages, so cargo --locked still rejected it. Version-only, matching what cargo writes.
Summary
vendor/tinyskills→ v0.5.2,vendor/tiny-artifacts→ v0.1.1,vendor/tinyhumans-sdk→ rust-v0.2.1.Cargo.lockchanges only the four version lines.Problem
Solution
main, and every old pin is an ancestor of its tag.[patch]tables, so no code changes.cargo update -pof these packages also re-targets unrelatedwindows-sysedges and downgrades tempfile'sgetrandom0.4.3 → 0.3.4. That churn is not part of this bump, so the lock keeps main's edges and changes only the four version lines.cargo metadata --lockedaccepts it without rewriting the file.Verified on a Linux CI runner against main e8707ea (baseline run): no new failing checks, and rust-core-coverage has the same 8 failing test names as main (0 new, 0 fixed). No lane rejected the lock under
--locked.static:rust-fmtandstatic:agent-runtime-boundaryfail identically on main. The branch merges cleanly with current main 0caf743.Submission Checklist
Impact
Related
Summary by CodeRabbit