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

[langfuse-bot]

Greptile Summary

Updates generated blob-storage integration API documentation to clarify the accepted region format and normalization behavior.

• Expands region parameter documentation in synchronous and asynchronous clients.
• Applies the same description to the generated request model.

Confidence Score: 5/5

The PR appears safe to merge because it only clarifies generated API documentation and introduces no runtime changes.

The changes are limited to consistent region docstring updates across the generated request model and client surfaces, with no accepted correctness, security, or compatibility failures.

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

[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, docstring-only change with no logic impact.

Reviewed: confirmed via full diff that the only changes are docstring text for the region field/parameter, expanded from "Storage region" to a more detailed description, repeated identically across client.py, raw_client.py, and the Pydantic type file. No code paths, validation, signatures, or types were touched.

Extended reasoning...

Overview

This PR (auto-generated from the langfuse/langfuse API spec, commit c8207ff) touches three files under langfuse/api/blob_storage_integrations/: client.py, raw_client.py, and types/create_blob_storage_integration_request.py. All four hunks are identical in nature: the docstring/description for the region field is expanded from the terse "Storage region" to a longer explanation of accepted formats and examples (S3-compatible providers, whitespace trimming, character/length constraints, sample values). I verified this directly by running the diff.

Security risks

None. No executable code, validation logic, request/response handling, or type definitions changed — only free-text docstrings/Field descriptions. There is no way this affects auth, data handling, or any runtime behavior.

Level of scrutiny

Minimal scrutiny is appropriate here. The change is confined to generated SDK documentation strings, is textually identical across all four occurrences, and has zero functional surface area. This is a textbook case of a safe, mechanical change.

Other factors

The files are Fern-style auto-generated API client code, so this description update presumably originates from an upstream OpenAPI spec change rather than a hand-edit, which is consistent with normal repo conventions for this SDK. No test changes are needed since no behavior changed. No CLAUDE.md or CODEOWNERS constraints apply. The bug-hunting pass reported no findings.