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

[langfuse-bot]

Greptile Summary

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

• Clarifies supported S3-compatible providers and region examples.
• Documents whitespace normalization and accepted region syntax consistently across synchronous, asynchronous, raw, and typed client surfaces.

Confidence Score: 5/5

The PR appears safe to merge because it only updates generated API documentation consistently across the affected surfaces.

No actionable failures remain; the request contract, serialization path, and runtime behavior are unchanged.

_{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]

Looks good, purely a docstring/comment update to auto-generated client code.

What was reviewed: the region docstring change across client.py, raw_client.py, and the pydantic Field docstring in create_blob_storage_integration_request.py. Confirmed no functional code, validation logic, or pydantic Field() arguments were touched — only the descriptive text was expanded to clarify accepted region formats.

Extended reasoning...

Overview

This PR (auto-generated from an upstream API spec sync) touches three files in the auto-generated blob_storage_integrations API client: client.py, raw_client.py, and types/create_blob_storage_integration_request.py. The diff only expands the docstring text for the region parameter/field from "Storage region" to a longer description explaining accepted formats (S3-compatible providers, Azure location IDs, length/character constraints, examples). No pydantic Field() arguments, validators, or any runtime logic were changed.

Security risks

None. This is a documentation-only change with no effect on request construction, validation, or data handling at runtime.

Level of scrutiny

Low. The change is mechanical, generated, and confined to comment/docstring text repeated identically across the three files (client, raw client, and type definition), consistent with a Fern-style codegen pipeline reacting to an upstream OpenAPI spec update. There is no ambiguity in intent and nothing to test since no behavior changed.

Other factors

The new docstring text describes validation rules (1-63 chars, no leading/trailing hyphen, etc.) that are not actually enforced anywhere in this diff — that's a legitimate discrepancy between documentation and enforcement, but it's an upstream spec/generator concern (the actual validation, if any, would need to be added to the OpenAPI spec that generates this client), not something to fix by hand in this auto-generated file. It doesn't introduce a bug in this codebase and isn't worth blocking or commenting on for a docstring-only PR.