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

[langfuse-bot]

Greptile Summary

Updates the generated blob-storage integration request documentation to clarify supported region formats, normalization, constraints, and examples.

• Expands the region field description without changing runtime behavior or the public TypeScript shape.

Confidence Score: 5/5

The PR appears safe to merge because it only clarifies generated API documentation and introduces no runtime or type-level behavior change.

The request remains serialized unchanged, and the expanded comment consistently describes server-owned region normalization and validation semantics.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
langfuse-js	Ready	Preview	Sep 2, 2026 4:28pm UTC

[github-actions]

@claude review

[claude]

LGTM — a purely mechanical JSDoc comment expansion in an auto-generated API types file, with no logic, type, or runtime changes.

Extended reasoning...

Overview

The diff touches exactly one line in packages/core/src/api/api/resources/blobStorageIntegrations/types/CreateBlobStorageIntegrationRequest.ts, a generated TypeScript types file. It expands the JSDoc comment on the region field from "Storage region" to a more detailed description covering supported cloud providers and validation rules (1-63 alphanumeric/hyphen characters, no leading/trailing hyphen) plus examples. No field names, types, optionality, or exported interfaces changed.

Security risks

None. This is a comment-only change; no code paths, validation logic, or data handling are affected.

Level of scrutiny

Very low. This is exactly the kind of mechanical, auto-generated (likely Fern/OpenAPI spec sync) documentation change that warrants minimal review — it is small, self-contained, and has an obviously correct and low-risk nature.

Other factors

The bug hunter reported no findings and the PR conversation timeline shows no outstanding objections. The file path itself signals this is machine-generated from an upstream API spec, so drift concerns are minimal since it will be regenerated on the next spec sync.