feat(api): update API spec from langfuse/langfuse 734325b

[langfuse-bot]

Greptile Summary

Updates the generated blob-storage integration API documentation to describe region normalization, validation constraints, and accepted examples consistently across synchronous, asynchronous, raw, and typed request surfaces.

• Expands the region parameter documentation in sync and async clients.
• Applies the same description to raw clients and CreateBlobStorageIntegrationRequest.

Confidence Score: 5/5

The PR appears safe to merge because it only updates consistent documentation for an existing API field.

The diff makes no executable, validation, serialization, transport, or public type changes, and no actionable defects were identified.

_{Reviews (1): Last reviewed commit: "feat(api): update API spec from langfuse..." | Re-trigger Greptile}

[github-actions]

@claude review

[claude]

LGTM — this is a purely mechanical, auto-generated documentation update.

What was reviewed: confirmed via full diff that all three files only change the region docstring/comment text (client.py, raw_client.py, and the CreateBlobStorageIntegrationRequest pydantic Field docstring) in the auto-generated API client. No code paths, validation logic, or signatures changed — the expanded text documents server-side constraints but doesn't add or alter any client-side validation.

Extended reasoning...

Overview

This PR is an auto-generated update to the Langfuse Python API client (fern-generated), syncing docstrings from the upstream OpenAPI spec for the blob_storage_integrations module. It touches three files: client.py, raw_client.py, and types/create_blob_storage_integration_request.py. In each, the only change is expanding the region parameter/field docstring from "Storage region" to a longer description of accepted formats and validation rules used server-side.

Security risks

None. No executable code changed — only docstring/comment strings. There is no new input handling, no injection surface, no auth/permission logic touched, and no change to request serialization or validation behavior.

Level of scrutiny

Low. This is a mechanical, auto-generated diff limited to comments/docstrings in generated API client code, with no functional impact. It matches the pattern of routine spec-sync PRs from the langfuse-bot.

Other factors

The candidate concern noted (that the new docstring implies validation constraints not actually implemented client-side) is expected and not a bug: this is a typed HTTP client wrapping a REST API: validation of the region string format is presumably enforced server-side, and the client docstring merely documents that. There's no indication this client is meant to pre-validate. No tests are needed for a comment-only change, and the bug-hunting pass found no issues.