chore(flows): bump vendored tinyflows → 0.5.1 (dotted-path split_out)#4608
Conversation
…t_out) Pulls tinyhumansai/tinyflows#4: split_out now resolves dotted paths, so a fan-out can reach an array nested inside a tool_call's {json,text,raw} envelope (path='json.data.messages'). Pairs with the live-tool-contract grounding (tinyhumansai#4605), which teaches the builder to write that exact path via the tool's primary_array_path — together they make fetch → split → per-item agent actually pass data. cargo check clean with 0.5.1 (backward compatible; single-segment paths unchanged).
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 29 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
Comment |
![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: 83229966b5
ℹ️ 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".
| [[package]] | ||
| name = "tinyflows" | ||
| version = "0.5.0" | ||
| version = "0.5.1" |
There was a problem hiding this comment.
This updates the root lockfile to tinyflows 0.5.1, but the Tauri shell is a separate Cargo world and app/src-tauri/Cargo.toml also depends on ../../vendor/tinyflows; its committed app/src-tauri/Cargo.lock still records tinyflows as 0.5.0. In locked/frozen Tauri cargo invocations, and in tooling that audits or releases from the committed Tauri lockfile, the lockfile is now inconsistent with the vendored package and misses the 0.5.1 metadata. Please regenerate and commit app/src-tauri/Cargo.lock alongside this bump.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in bf8f0c9 — regenerated app/src-tauri/Cargo.lock with a targeted bump of the tinyflows entry to 0.5.1 (verified cargo check --manifest-path app/src-tauri/Cargo.toml --locked passes). Kept the diff to just the version line since tinyflows's own dependency footprint is unchanged between 0.5.0 and 0.5.1.
…split_out) tinyhumansai/tinyflows#4 squash-merged; pin to the main commit instead of the feature-branch commit so CI resolves the submodule cleanly.
2 participants
Bumps the vendored
tinyflowssubmodule to 0.5.1 (tinyhumansai/tinyflows#4):split_outnow resolves dotted paths, so a fan-out can reach an array nested inside a tool_call's{json,text,raw}envelope —path="json.data.messages"walks envelope → tool result → the array (e.g.GMAIL_FETCH_EMAILS's list atdata.messages).Pairs with #4605 (live tool-contract grounding): #4605 teaches the builder to write the correct
json.<primary_array_path>via the tool's real output schema; this bump makes the engine traverse it. Together,fetch → split_out → per-item agentfinally passes real data (fixes the null-cascade in the classify-emails flow).Backward compatible: single-segment paths (
path="items") unchanged.cargo checkclean with 0.5.1.