feat(api): add File contents method and physical_check_book event category#1386
Merged
Conversation
Closed
increase-releases
Bot
changed the title
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the SDK up to the latest spec. Because this repo was a spec release behind, this sync bundles more than the rest of the batch:
contentsmethod on the File service (GET /files/{file_id}/contents) for downloading a File's contents, together with itsFileContentsParams.physical_check_book.createdandphysical_check_book.updatedmembers to the event category enums.X-Stainless-*telemetry / timeout / retry-count request headers from the HTTP client plumbing (no public typed-API surface change).Held for manual review — diff is materially larger than and inconsistent with the rest of this batch. Unlike the other SDKs (which received only the event-category enum addition), this PR also carries catch-up library changes — a new endpoint plus removal of the
X-Stainless-*request headers. A human should confirm the header-behavior change before merging.Spec:
ea35154a418c5a3cabaedc30f766fcac.