Update API specifications with fern api update#71
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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
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.
Update API specifications by running fern api update.
Note
Medium Risk
Primarily updates generated/spec files, but any spec-level changes can be breaking for downstream SDKs/docs if endpoints or schemas changed.
Overview
Updates the repository’s API specification outputs by re-running
fern api update, refreshing the tracked spec artifacts to the latest generated versions.Reviewers should focus on any semantic API diffs (endpoint signatures, request/response schemas, error models) that could impact generated SDKs or docs.
Reviewed by Cursor Bugbot for commit 3605137. Bugbot is set up for automated code reviews on this repo. Configure here.