release: 0.10.4#338
Open
stainless-app[bot] wants to merge 4 commits intomainfrom
Open
Conversation
add service account id as option to register agentex agent
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.10.4 (2026-04-30)
Full Changelog: v0.10.3...v0.10.4
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 patch release (0.10.4) adds support for
service_account_idas an alternative touser_idin the auth principal config, so agents can be registered under a service account rather than a personal identity. Validation is updated to enforce an XOR constraint (exactly one of the two fields must be set), and four new unit tests cover the expected pass/reject cases.Confidence Score: 5/5
Safe to merge — the XOR logic is correct, backwards-compatible, and covered by tests.
All findings are at P2 or lower; the core validation change is straightforward and well-tested with four dedicated cases. Version bumps are consistent across all files.
No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[validate_environments_config] --> B[_validate_single_environment_config] B --> C{principal has user_id?} C -- Yes --> D{principal also has service_account_id?} C -- No --> E{principal has service_account_id?} E -- No --> F[❌ ValueError: must have one of user_id or service_account_id] E -- Yes --> G[✅ Continue validation] D -- Yes --> H[❌ ValueError: cannot have both] D -- No --> I[Check user_id env-name pattern ⚠️ warn if missing] I --> J[Validate helm_overrides] G --> JReviews (1): Last reviewed commit: "release: 0.10.4" | Re-trigger Greptile