Release v0.8.0

[lchoquel]

Publishes pipelex-sdk v0.8.0 to PyPI on merge (the push to main triggers publish.yml): the method-selectors release — method_ref as a typed run source with typed provenance, method_ref/method_id selectors on validate, the new resolve/codegen crate routes with the method_id pass-through, the shared files XOR method_ref closure on build_inputs, and the fetch-sized budget for method_ref closures. See the ## [v0.8.0] changelog section.

Merge order: land #19 (feature/Method-selectors → dev) first, then this one — the two branches carry the same commit today; if review rounds add commits to #19, update this branch before merging.

Advances L-260828-12fa7b

🤖 Generated with Claude Code

https://claude.ai/code/session_01WoLcQhnFiPgVmDzHqPkRmQ

---

Summary by cubic

Publishes pipelex-sdk v0.8.0 to PyPI on merge: the method-selectors release. Adds method_ref as a typed, self-contained run source on execute, start, and start_and_wait — the runner resolves the address, and provenance (address, tag, fetched commit SHA) comes back typed on both run paths — plus method_ref/method_id selectors on validate, the new /v1/resolve and /v1/codegen routes, and the files XOR method_ref closure on build_inputs. On the tooling routes, empty selectors (files=[ ], empty method_ref/method_id) normalize to absent before the XOR, so an empty value alone fails the closure and an empty value beside a real selector is never sent. The new selectors require pipelex-api >= 0.21.0; on api.pipelex.com availability follows the platform deploy.

Merge order

• Land Method selectors: method_ref run source + tooling-route method_id, crate routes added #19 first — both branches carry the same commit today; if review adds commits to Method selectors: method_ref run source + tooling-route method_id, crate routes added #19, update this branch before merging.

Advances L-260828-12fa7b.

^{Written for commit a2f7b03. Summary will update on new commits.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T03:41:13.278117Z	9862ab6	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.

[greptile-apps]

Confidence Score: 4/5

The empty crate selectors should be rejected at construction before merging because the current models forward invalid request bodies to all three crate-family routes.

The new XOR validators use non-None presence checks, so empty files and method references pass model construction and are serialized unchanged despite not identifying a usable closure.

Files Needing Attention: pipelex_sdk/build_models.py, pipelex_sdk/crate_models.py

Prompt To Fix All With AI

### Issue 1
pipelex_sdk/build_models.py:86
**Empty selectors pass validation**

When a caller supplies `files=[]` or `method_ref=""`, the non-`None` XOR checks accept it as a selected closure and `model_dump(exclude_none=True)` sends the empty value unchanged, causing a server request-shape error instead of rejecting the invalid closure at the SDK boundary. The same issue applies to the selector validator in `CrateToolingRequest`.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Both method selectors in one pass: metho..." | Re-trigger Greptile}

[greptile-apps]

Empty selectors pass validation

When a caller supplies files=[] or method_ref="", the non-None XOR checks accept it as a selected closure and model_dump(exclude_none=True) sends the empty value unchanged, causing a server request-shape error instead of rejecting the invalid closure at the SDK boundary. The same issue applies to the selector validator in CrateToolingRequest.

Knowledge Base Used: Buildinputmodels

Prompt To Fix With AI

This is a comment left during a code review.
Path: pipelex_sdk/build_models.py
Line: 86

Comment:
**Empty selectors pass validation**

When a caller supplies `files=[]` or `method_ref=""`, the non-`None` XOR checks accept it as a selected closure and `model_dump(exclude_none=True)` sends the empty value unchanged, causing a server request-shape error instead of rejecting the invalid closure at the SDK boundary. The same issue applies to the selector validator in `CrateToolingRequest`.

**Knowledge Base Used:** [Buildinputmodels](https://app.greptile.com/pipelex/-/custom-context/knowledge-base/pipelex/pipelex-sdk-python/-/docs/build-input-models.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.