release: 0.25.0

[stainless-app]

Automated Release PR

0.25.0 (2026-01-07)

Full Changelog: v0.24.0...v0.25.0

Features

• api: add health check endpoint for proxies (c7b8728)
• auth: add auto_login credential flow (2eec1a1)
• Enhance AuthAgentInvocation with step and last activity tracking (ccb1425)

Bug Fixes

• skip usage tests that don't work with Prism (8872193)

Chores

• add float64 to valid types for RegisterFieldValidator (1e23b39)
• internal: codegen related update (e07718d)
• internal: codegen related update (0320876)

---

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

---

Note

Releases v0.25.0 with notable API surface updates across auth, credentials, and proxies.

• Auth: Unifies AuthAgentInvocationCreateResponse (always returns invocation_id), enriches AgentAuthInvocationResponse with domain, type, step, FAILED status, SSO button metadata, submitted/pending fields, and live_view_url; DiscoveredField adds totp. AuthAgent/create params add allowed_domains; list query switches to domain (removes target_domain). Submit becomes a union (field_values or sso_button) and returns accepted; removes reauth and discover endpoints and related types.
• Credentials: Endpoints accept id_or_name; add TOTP support (totp_secret on create/update, has_totp_secret, transient totp_code + expiry) and optional sso_provider; values now merge on update; new GET /credentials/{id_or_name}/totp-code.
• Proxies: Adds health check POST /proxies/{id}/check and ProxyCheckResponse types.
• Internals/Docs: Bumps version to 0.25.0, updates README pin, LICENSE year, enum validator supports float64, and regenerates api.md/tests.

^{Written by Cursor Bugbot for commit 07bdf87. This will update automatically on new commits. Configure here.}

[cursor]

Bug: float64 type added but not handled in switch

The type constraint for RegisterFieldValidator was expanded to accept float64 values, but the switch statement inside the function (handling []string, []int, []bool) has no case []float64: branch. Additionally, validationEntry.legalValues has no field for storing float64 values, and no validateFloat function exists. If float64 values are passed to this function, they will be silently ignored and validation will not work correctly.

 

[masnwilliams]

lgtm