release: 0.12.0#350
Open
stainless-app[bot] wants to merge 4 commits intomainfrom
Open
Conversation
cac40be to
c646eb3
Compare
…plates (#352) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
c646eb3 to
7ad5b19
Compare
7ad5b19 to
5eaf474
Compare
5eaf474 to
ec02cb4
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.
Automated Release PR
0.12.0 (2026-05-08)
Full Changelog: v0.11.0...v0.12.0
⚠ BREAKING CHANGES
Features
Bug Fixes
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
AgentexTracingProcessorConfigas the default tracing processor (breaking change), fixes a missing f-string prefix in_files.py, and addsSGP_CLIENT_BASE_URLsupport +set_tracing_disabled(True)across all CLI project templates.temporal-openai-agents/workflow.py.j2template callsadd_tracing_processor_configunconditionally with potentially empty credentials, unlike the guarded pattern used inacp.py.j2, which will cause runtime tracing errors for users who haven't configured SGP credentials.Confidence Score: 4/5
Safe to merge with one P1 fix — unconditional tracing registration in the temporal-openai-agents template should be guarded like its sibling.
One P1 finding: the temporal-openai-agents workflow template registers an SGP tracing processor unconditionally, which causes auth errors at runtime for users without SGP credentials. All other changes are clean. P1 ceiling is 4/5.
src/agentex/lib/cli/templates/temporal-openai-agents/project/workflow.py.j2
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Agent template starts] --> B{Template type?} B --> |sync-openai-agents / acp.py.j2| C[set_tracing_disabled - True] B --> |temporal-openai-agents / workflow.py.j2| D[set_tracing_disabled - True] C --> E{SGP_API_KEY AND SGP_ACCOUNT_ID set?} E --> |Yes| F[add_tracing_processor_config with credentials + base_url] E --> |No| G[Skip — no processor registered] D --> H[add_tracing_processor_config - ALWAYS - even if empty creds] H --> I[SGPTracingProcessor registered with empty strings] I --> J[Auth errors on every trace event] style H fill:#ff6b6b,color:#fff style I fill:#ff6b6b,color:#fff style J fill:#ff6b6b,color:#fff style G fill:#51cf66,color:#fff style F fill:#51cf66,color:#fffComments Outside Diff (1)
src/agentex/lib/cli/templates/temporal-openai-agents/project/workflow.py.j2, line 44-50 (link)add_tracing_processor_configis called unconditionally regardless of whetherSGP_API_KEYandSGP_ACCOUNT_IDare set. Any user who generates this template without SGP credentials will have a tracing processor registered that tries to authenticate against SGP with empty strings on every trace event, producing auth errors at runtime. The sibling templateacp.py.j2guards this call withif SGP_API_KEY and SGP_ACCOUNT_ID:— the same guard should be applied here.Prompt To Fix With AI
Prompt To Fix All With AI
Reviews (4): Last reviewed commit: "release: 0.12.0" | Re-trigger Greptile