chore: release main - #475
Merged
deepthi-rao-scale merged 4 commits intoJul 29, 2026
Merged
Conversation
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Nitesh Dhanpal <NiteshDhanpal@users.noreply.github.com> Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
…#455) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 29, 2026 15:35
cd5a3c5 to
36cc1a8
Compare
…s can't ship stale source (#476) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 29, 2026 20:52
36cc1a8 to
ed44857
Compare
deepthi-rao-scale
approved these changes
Jul 29, 2026
deepthi-rao-scale
enabled auto-merge (squash)
July 29, 2026 21:13
deepthi-rao-scale
deleted the
release-please--branches--main--changes--next
branch
July 29, 2026 21:20
Contributor
Author
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Stainless prepared a new release
agentex-client: 0.22.0
0.22.0 (2026-07-29)
Full Changelog: agentex-client-v0.21.0...agentex-client-v0.22.0
Features
Bug Fixes
Refactors
agentex-sdk: 0.22.0
0.22.0 (2026-07-29)
Full Changelog: agentex-sdk-v0.21.0...agentex-sdk-v0.22.0
Chores
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 buildto--no-cache, and removal of the oldbuild-info.jsonregistration read-path.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 toNoneso they never break a build.iter_context_filesis also reused inBuildContextManager.zipped()to make the tar archive order deterministic and consistent with the hash.--no-cachedefault:agentex agents buildnow passescache=Falsetodocker.buildx.build()(confirmed:python_on_whalesmaps this to--no-cache), preventing stale cached layers from silently shipping outdated source. Users can opt back in with--cache.FastACP.locate_build_info_path(),get_build_info(),BUILD_INFO_PATHenv 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 fieldsPrompt To Fix All With AI
Reviews (3): Last reviewed commit: "chore: release main" | Re-trigger Greptile