Skip to content

chore: release main#404

Open
stainless-app[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--changes--next
Open

chore: release main#404
stainless-app[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

✨ Stainless prepared a new release

agentex-client: 0.13.1

0.13.1 (2026-06-17)

Full Changelog: agentex-client-v0.13.0...agentex-client-v0.13.1

Bug Fixes

  • adk: re-send task_id/agent_id in state updates for backend compatibility (#405) (f59f26d)

Documentation

  • drop stale keep_files / dashboard-config comments (#401) (23858df)
agentex-sdk: 0.13.1

0.13.1 (2026-06-17)

Full Changelog: agentex-sdk-v0.13.0...agentex-sdk-v0.13.1

Documentation

  • drop stale keep_files / dashboard-config comments (#401) (23858df)

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

  • Prepares the 0.13.1 release for the client and ADK packages.
  • Updates release metadata, package versions, and changelog entries.
  • Restores ADK state update compatibility by sending task_id and agent_id in update request bodies.
  • Adds regression coverage for the ADK state update request body.
  • Removes stale generated documentation comments around keep_files and dashboard configuration.

Confidence Score: 5/5

Safe to merge.

The changes are limited to release metadata, documentation cleanup, a targeted ADK compatibility fix, and matching regression coverage.

T-Rex T-Rex Logs

What T-Rex did

  • The regression test for states.update kwargs was executed and passed, confirming the payload change added extra_body with agent_id a1 and task_id t1.
  • Release metadata docs validation was run and compared across two commits, showing before state 0.13.0 with no 0.13.1 changelog entries and after state 0.13.1 with appropriate changelog sections and cleaned README/pyproject metadata.

View all artifacts

T-Rex Ran code and verified through T-Rex

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

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
max-parke-scale and others added 2 commits June 17, 2026 12:41
…tibility (#405)

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 329dcdc to eba669f Compare June 17, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant