feat(api): update API spec from langfuse/langfuse 7cd0bc0

[langfuse-bot]

Greptile Summary

Updates the generated feedback API documentation to clarify regional availability.

• Notes that feedback submission is unavailable in the HIPAA cloud region.
• Applies the clarification consistently across synchronous, asynchronous, parsed-response, and raw-response clients.

Confidence Score: 5/5

The PR appears safe to merge because it changes documentation only and keeps all feedback client variants aligned.

The changes add matching regional-availability notes to four method docstrings and do not alter imports, request handling, API contracts, or runtime execution.

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

[github-actions]

@claude review

[claude]

Looks good, docstring-only change. Verified the diff only inserts the sentence "Not available in the HIPAA cloud region." into the existing docstrings of the feedback create method in FeedbackClient, AsyncFeedbackClient, RawFeedbackClient, and AsyncRawFeedbackClient — no signatures, logic, or behavior are touched.

Extended reasoning...

Overview

This PR (auto-generated by langfuse-bot from an upstream API spec update) touches two files under langfuse/api/feedback/: client.py and raw_client.py. In each file, a single new sentence is added to the docstring of the feedback-submission method, appearing identically in the sync and async client variants (four insertion points total). I ran the diff directly and confirmed there are no changes to method signatures, parameter lists, return types, control flow, or any other code — purely a docstring text addition.

Security risks

None. No code paths, request construction, auth handling, or data serialization are affected. Adding an informational note about HIPAA cloud region availability to a docstring has no security surface.

Level of scrutiny

This warrants minimal scrutiny — it is a mechanical, auto-generated documentation update with no logic changes, consistent across both files/four classes, matching the pattern of prior auto-generated spec-sync PRs. No CODEOWNERS or CLAUDE.md constraints apply here (none found for these paths).

Other factors

No bug findings were reported by the bug hunting system, and my own read of the full diff corroborates that assessment — the change is trivially verifiable by inspection. No test coverage concerns arise since no executable behavior changed.