✨ Stainless prepared a new release

0.22.0 (2026-07-29)

Full Changelog: agentex-client-v0.21.0...agentex-client-v0.22.0

Features

• lib: capture client-attested build provenance (#454) (8964044)

Bug Fixes

• lib: default 'agentex agents build' to --no-cache so stale layers can't ship stale source (#476) (632d82c)

Refactors

• lib: remove the dead build-info.json registration read-path (#455) (2078f9f)

0.22.0 (2026-07-29)

Full Changelog: agentex-sdk-v0.21.0...agentex-sdk-v0.22.0

Chores

• agentex-sdk: Synchronize agentex versions

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

Greptile Summary

This release (0.22.0) bundles three merged PRs: client-attested build provenance capture, defaulting agentex agents build to --no-cache, and removal of the old build-info.json registration read-path.

• Build provenance (build_provenance.py): new module computes a deterministic working-tree hash over sorted files/symlinks and collects git coordinates (commit, ref, remote, dirty flag, author). All failures degrade gracefully to None so they never break a build. iter_context_files is also reused in BuildContextManager.zipped() to make the tar archive order deterministic and consistent with the hash.
• --no-cache default: agentex agents build now passes cache=False to docker.buildx.build() (confirmed: python_on_whales maps this to --no-cache), preventing stale cached layers from silently shipping outdated source. Users can opt back in with --cache.
• Dead-code removal: FastACP.locate_build_info_path(), get_build_info(), BUILD_INFO_PATH env var, and related env model field are all removed; registration metadata now starts from an empty dict.

Confidence Score: 4/5

Functionally correct but the committed uv.lock is one version behind pyproject.toml, which will break any CI job using uv sync --frozen.

The new provenance module is well-written and gracefully degrades, the --no-cache default is correctly wired through python_on_whales, and the dead-code removal is clean. The only blocker is that uv.lock still records 0.21.0 while pyproject.toml now says 0.22.0 — any frozen-lock CI step will fail until uv lock is re-run and the result committed.

Files Needing Attention: uv.lock needs to be regenerated with uv lock to reflect the 0.22.0 version bump before this can merge without breaking CI.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant CLI as agentex agents build
    participant AH as agent_handlers.build_agent()
    participant BP as build_provenance
    participant BCM as BuildContextManager
    participant Docker as docker.buildx.build()

    CLI->>AH: "build_agent(manifest, ..., cache=False)"
    AH->>BCM: build_context_manager(manifest, root)
    BCM->>BP: iter_context_files(root)
    BP-->>BCM: sorted [files + symlinks]
    BCM->>BCM: zipped() → tar.gz archive
    BCM-->>AH: build_context
    AH->>Docker: "buildx.build(cache=False, ...)"
    Note over Docker: --no-cache flag sent to Docker
    AH->>BP: capture_build_provenance(repo_path, context_root)
    BP->>BP: _git rev-parse, symbolic-ref, log
    BP->>BP: working_tree_hash(root)
    BP-->>AH: "BuildProvenance{commit, ref, dirty, hash, ...}"
    AH->>AH: provenance.source_fields() → upload form fields

### Issue 1
uv.lock:17-19
**Lock file one version behind pyproject.toml**

After this PR lands, `pyproject.toml` declares `0.22.0` for both packages but `uv.lock` records `0.21.0`. Any CI step that runs `uv sync --frozen` (which locks the environment to the committed lock file) will fail immediately with a "lock file out of date" error, because uv detects the version mismatch between the workspace member's `pyproject.toml` and what the lock file expects. Run `uv lock` locally and commit the refreshed `uv.lock` to fix this.

---

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

Reviews (3): Last reviewed commit: "chore: release main" | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.