chore: release main#464
Open
stainless-app[bot] wants to merge 4 commits into
Open
Conversation
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 18:29
7f14903 to
e70f46e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 23:06
e70f46e to
74d4c40
Compare
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.21.0
0.21.0 (2026-07-21)
Full Changelog: agentex-client-v0.20.0...agentex-client-v0.21.0
Features
agentex-sdk: 0.21.0
0.21.0 (2026-07-21)
Full Changelog: agentex-sdk-v0.20.0...agentex-sdk-v0.21.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 is a Stainless-generated release PR bumping both
agentex-clientandagentex-sdkfrom 0.20.0 to 0.21.0. The substantive API change adds aninclude_livequery parameter to the schedules list endpoint and a correspondinglive_data_availableresponse field across all schedule response models.include_liveparameter: Added toScheduleListParams, wired into themaybe_transformquery dict for both the sync and asynclistmethods, and covered by updated tests.live_data_availablefield: Consistently added asOptional[bool] = Noneto all 13 schedule response models;nullsignals the field was not requested,true/falseindicates whether live Temporal enrichment succeeded.stainless-sdks/agentex-sdk-pythonto a prefix match (startsWith(github.repository, 'stainless-sdks/')) to support private production repos under the same org.Confidence Score: 5/5
Safe to merge — all changes are additive (new optional parameter, new optional response field) with no breaking changes to existing callers.
The
include_liveparameter defaults toomitso existing callers are unaffected. Thelive_data_availablefield isOptional[bool] = Noneon every response model, so deserialization of old API responses remains valid. The CI runner broadening is an intentional, scoped change. No logic errors or regressions identified.No files require special attention.
Important Files Changed
startsWith(github.repository, 'stainless-sdks/')) to support private production repos under the same org prefix.include_live: booloptional field toScheduleListParamsTypedDict with accurate docstring.live_data_available: Optional[bool] = NonetoRunSchedulemodel, nullable to indicate enrichment was not requested.live_data_available: Optional[bool] = Nonefield consistent with the rest of the schedule response models.test_method_list_with_all_paramstests to passinclude_live=True, covering the new parameter.Sequence Diagram
%%{init: {'theme': 'neutral'}}%% sequenceDiagram participant Caller participant SchedulesResource participant AgentexAPI Caller->>SchedulesResource: "list(agent_id, include_live=True, limit=N)" SchedulesResource->>AgentexAPI: "GET /agents/{agent_id}/schedules?include_live=true&limit=N" AgentexAPI-->>SchedulesResource: RunSchedule[] (with live_data_available, next_action_times) SchedulesResource-->>Caller: ScheduleListResponse Caller->>SchedulesResource: "list(agent_id, limit=N)" SchedulesResource->>AgentexAPI: "GET /agents/{agent_id}/schedules?limit=N" AgentexAPI-->>SchedulesResource: "RunSchedule[] (live_data_available=null)" SchedulesResource-->>Caller: ScheduleListResponse%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% sequenceDiagram participant Caller participant SchedulesResource participant AgentexAPI Caller->>SchedulesResource: "list(agent_id, include_live=True, limit=N)" SchedulesResource->>AgentexAPI: "GET /agents/{agent_id}/schedules?include_live=true&limit=N" AgentexAPI-->>SchedulesResource: RunSchedule[] (with live_data_available, next_action_times) SchedulesResource-->>Caller: ScheduleListResponse Caller->>SchedulesResource: "list(agent_id, limit=N)" SchedulesResource->>AgentexAPI: "GET /agents/{agent_id}/schedules?limit=N" AgentexAPI-->>SchedulesResource: "RunSchedule[] (live_data_available=null)" SchedulesResource-->>Caller: ScheduleListResponseReviews (3): Last reviewed commit: "chore: release main" | Re-trigger Greptile