feat(api): update API spec from langfuse/langfuse b1290b4

[langfuse-bot]

Greptile Summary

This PR refreshes generated blob-storage API documentation for the region field.

• Clarifies supported S3-compatible providers and region examples.
• Documents server-side whitespace normalization and format constraints.
• Applies the same description across synchronous, asynchronous, raw, and typed request surfaces.

Confidence Score: 5/5

The PR appears safe to merge because it changes documentation consistently without altering runtime behavior or public types.

The three changed files consistently describe the same existing server-side region contract, and no concrete correctness, security, or repository-rule violation remains.

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

Context used:

• Knowledge Base — Generated API service domains

[github-actions]

@claude review

[claude]

Claude Code Review

No review was started: this request came from a bot account. Manual reviews can only be requested by someone with write access to this repository. Ask a maintainer to comment @claude review, or have your automation post the comment from a user account with write access.

_{Tip: disable this comment in your organization's Code Review settings.}

[claude]

LGTM, purely a docstring update.

What was reviewed: confirmed the diff only touches the region parameter docstring in the auto-generated client.py, raw_client.py, and the pydantic field docstring in create_blob_storage_integration_request.py — checked that no method signatures, types, or validation logic changed anywhere in the diff.

Extended reasoning...

Overview

This PR is an auto-generated API-spec sync (langfuse-bot) that touches three files under langfuse/api/blob_storage_integrations/: client.py, raw_client.py, and types/create_blob_storage_integration_request.py. The only change is expanding the docstring/description for the region field from "Storage region" to a longer explanation of accepted formats (S3-compatible clients, Azure location IDs, OCI), whitespace handling, and length/character constraints, with examples. This same text is repeated identically across the sync and async client classes in both client.py and raw_client.py, plus the pydantic field docstring.

Security risks

None. No code paths, validation, network calls, or data handling were modified — only human-readable text in docstrings/comments.

Level of scrutiny

Low. This is a mechanical, auto-generated documentation-only change with no behavioral impact. It matches the pattern of typo/comment fixes explicitly called out as approvable.

Other factors

Verified via direct diff inspection that all four hunks are textually identical docstring replacements and that nothing else in the diff changes logic, types, or signatures. No CODEOWNERS file was found restricting this path. No outstanding review comments exist in the timeline to address.