feat(api): update API spec from langfuse/langfuse 07cae52

[langfuse-bot]

Disclaimer: Experimental PR review

Greptile Summary

This PR updates the docstring for bucket_name across the auto-generated blob_storage_integrations API files to clarify Azure Blob Storage container name constraints (3–63 chars, lowercase letters, numbers, and hyphens, must start/end with letter or number, no consecutive hyphens). The change is documentation-only and affects four locations: sync/async client.py, raw_client.py, and the CreateBlobStorageIntegrationRequest type.

Confidence Score: 5/5

Safe to merge — documentation-only update to auto-generated files with no logic changes.

All changes are docstring updates in auto-generated API files, consistently applied across all four client surfaces and the request type. No logic, validation, or behavior is modified.

No files require special attention.

Important Files Changed

Filename	Overview
langfuse/api/blob_storage_integrations/client.py	Docstring-only update to bucket_name parameter description in both sync and async clients, adding Azure container name constraints.
langfuse/api/blob_storage_integrations/raw_client.py	Docstring-only update to bucket_name parameter description in both sync and async raw clients, matching client.py changes.
langfuse/api/blob_storage_integrations/types/create_blob_storage_integration_request.py	Docstring-only update to bucket_name field description in the Pydantic model, consistent with client/raw_client changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[API Spec Update] --> B[bucket_name docstring updated]
    B --> C[client.py - sync BlobStorageIntegrationsClient]
    B --> D[client.py - async AsyncBlobStorageIntegrationsClient]
    B --> E[raw_client.py - sync RawBlobStorageIntegrationsClient]
    B --> F[raw_client.py - async AsyncRawBlobStorageIntegrationsClient]
    B --> G[types/create_blob_storage_integration_request.py]
    C & D & E & F & G --> H["Added: Azure container name constraints\n(3-63 chars, lowercase, hyphens, no consecutive hyphens)"]

Loading

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

[github-actions]

@claude review

[claude]

LGTM — purely a docstring update adding Azure container name validation constraints to the bucket_name parameter description.

Extended reasoning...

Overview\nThis PR updates 4 docstring occurrences across 3 auto-generated files (client.py, raw_client.py, and the CreateBlobStorageIntegrationRequest type). The only change is expanding the bucket_name parameter description from "Name of the storage bucket" to include Azure-specific container naming constraints. No logic, behavior, or interface changes are made.\n\n### Security risks\nNone. This is a documentation-only change with no code execution paths affected.\n\n### Level of scrutiny\nMinimal scrutiny required. The files are auto-generated by Fern from the API spec, and the change is a simple, consistent docstring update applied uniformly across all relevant locations.\n\n### Other factors\nNo bugs were found. No prior reviews on this PR. The change is self-consistent and accurately documents real Azure container naming constraints.

[blacksmith-sh]

Found 4 test failures on Blacksmith runners:

Failures

Test	View Logs
test_decorators/test_scoring_observations	View Logs
test_decorators/test_scoring_observations	View Logs
test_decorators/test_scoring_observations	View Logs
test_decorators/test_scoring_observations	View Logs

[claude]

LGTM — documentation-only update to auto-generated files.

Extended reasoning...

Overview\nThis PR updates docstrings for the parameter across three auto-generated API files (, , and ). The sole change is appending Azure container name constraints to the existing description string, applied consistently across all four client surfaces (sync/async × client/raw_client) and the Pydantic model.\n\n### Security risks\nNone. This is a documentation-only change with no logic, validation, or behavior modifications.\n\n### Level of scrutiny\nMinimal scrutiny required. These are auto-generated files with a purely additive docstring update. The CI failures () are entirely unrelated to the changed files and appear to be pre-existing test instability.\n\n### Other factors\nNo bugs were found by the bug hunting system. The change is internally consistent across all modified locations.