Repository navigation
chore(vendor): restore and advance the tinytools and tinyinference pins - #564
Conversation
An auto-commit (48aacf4) moved vendor/tinytools and vendor/tinyinference back to older commits, dropping the fixes the tinyhumansai#535 and tinyhumansai#537 bumps pinned. This moves both forward to the current mains.
Tiny Sweeper reviewReviewed head: Verdict: Ready for maintainer review · Priority: none Diagnostics and supporting detailsFull summaryPull request purpose (title): chore(vendor): restore and advance the tinytools and tinyinference pins. 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
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely describes restoring and advancing the tinytools and tinyinference vendor pins, which is the main 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. (2 skipped: 2 unsupported.)
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
A rabbit checks each pointer’s place
Two vendor paths now point elsewhere
New commit marks replace the old
No hidden contents can be told
The rabbit hops, review complete
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
Moves the pins past the restored commits to include the merged tinytools tinyhumansai#92-tinyhumansai#98 and tinyinference tinyhumansai#134-tinyhumansai#136, tinyhumansai#138, tinyhumansai#139. No vendor manifest changed, so Cargo.lock is unchanged.
M3gA-Mind
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
An auto-commit (48aacf4, "chore(vendor): bump tinyinference and tinytools submodules") moved these gitlinks back to older commits. That undid the forward bumps from #535 and #537. This PR moves both gitlinks forward again, to each repo's current main. Both old commits are ancestors of the new ones, so this is a fast-forward of each pin.
vendor/tinytools:3a01641→62dbb14(29 commits), then →75e42ba(17 more)vendor/tinyinference:e5d7092→8d33b80(20 commits), then →b21593f(11 more)The second commit moves both pins on to each repo's current main, which takes in the vendor PRs that merged after this PR was opened (listed at the end of each section below).
vendor/tinyliveagents: unchanged.Fixes this restores or brings in:
tinytools
{}.tinyinference
No manifest changed in either range. Both are path dependencies here, so
Cargo.lockis unchanged.API Or Behavior Changes
None to this repo's API. The vendor behaviour changes are the fixes listed above. They are the same ones #535 and #537 brought in, plus tinytools #90/#91 and tinyinference #128.
Tests
Gitlink-only; CI builds and tests the workspace against the restored pins. Each vendor PR carries its own regression test.
cargo fmt --check: no Rust source changed herecargo clippy --all-targets -- -D warnings: left to CIcargo clippy --all-targets --all-features -- -D warnings: left to CIcargo build --all-targets: left to CIcargo build --all-targets --all-features: left to CIcargo test: left to CIcargo test --all-features: left to CIDocumentation
Not needed: a vendor pin change.
Summary by CodeRabbit