Skip to content

release: 0.10.4#338

Open
stainless-app[bot] wants to merge 4 commits intomainfrom
release-please--branches--main--changes--next
Open

release: 0.10.4#338
stainless-app[bot] wants to merge 4 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented Apr 30, 2026

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_id as an alternative to user_id in 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

Filename Overview
src/agentex/lib/sdk/config/validation.py Replaces the old user_id-only check with a proper XOR guard; also extends the friendly error hint to cover both id fields. Logic is correct and well-scoped.
tests/lib/cli/test_validation.py New test file with four targeted cases covering backwards compat, new service_account_id path, missing-both, and set-both scenarios — all correctly verify the new XOR invariant.
src/agentex/lib/sdk/config/environment_config.py Docstring updated with a service_account_id YAML example; no logic changes.
src/agentex/_version.py Version bumped from 0.10.3 to 0.10.4.
pyproject.toml Version bumped from 0.10.3 to 0.10.4; no other changes.

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 --> J
Loading

Reviews (1): Last reviewed commit: "release: 0.10.4" | Re-trigger Greptile

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