Repository navigation
PAL-1311 Generate the CLI alongside the shared SDKs - #1422
Draft
chris-garber-vapi wants to merge 1 commit into
Draft
chris-garber-vapi wants to merge 1 commit into
chris-garber-vapi wants to merge 1 commit into
Conversation
[Replace the Vapi CLI with a Fern-generated OAuth beta](https://linear.app/vapi/issue/PAL-1311/replace-the-vapi-cli-with-a-fern-generated-oauth-beta) ## Description Configures CLI generation in this repository alongside the server SDKs. The new `cli-sdk` group targets `VapiAI/cli` in pull-request mode; Release CLI accepts an explicit version and opens a generated PR without publishing. ## How it works The CLI workspace references the existing API's OpenAPI file, naming overrides and parameter overlay directly. Its OAuth/PKCE and staging-server overrides stay isolated from the other SDKs. A separate workspace is necessary because generator-level spec overrides did not reach the CLI's embedded OpenAPI in validation. | Before | After | | --- | --- | | CLI vendors three API inputs and owns separate generation scripts | Shared files are consumed directly from this repo | | CLI generation runs separately | Central Release CLI workflow uses Fern's SDK PR delivery path | The seven existing SDK groups and their effective API configuration remain byte-for-byte unchanged. The paired [CLI #21](https://app.graphite.com/github/pr/VapiAI/cli/21) removes the duplicated inputs, retains repository-owned docs/tests, and uses native Fern Replay for schema and command-binding customizations. Its HTTP runtime is Fernignore-protected because Replay rejects the embedded public test certificate. ## Testing Steps - [x] Central publishing preview succeeds with native PKCE, the staging default server and optional provider Content-Type. - [x] Shared input paths/settings match the API workspace; existing SDK configuration is unchanged. - [x] Two local native Replay cycles preserve runtime, API files, wire fixtures and repository-owned checks without conflicts. - [x] CLI runtime tests (2,265), wire tests (290), end-to-end checks and 500 ms performance budgets pass. - [x] Workflow passes actionlint. ## Risks Merge CLI #21 before the first Release CLI invocation so the destination has its Replay baseline and Fernignore protections. Keep CLI generator 0.59.1 pinned; reconcile the protected HTTP runtime with fresh output when upgrading it. Live OAuth acceptance, production client promotion and package-publishing setup remain release gates. This PR does not publish a package or change server SDK authentication.
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a1d69f-d68a-73bd-a7dd-f290be143a47.docs.buildwithfern.com |
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.
Replace the Vapi CLI with a Fern-generated OAuth beta
Related PRs and rollout
Description
Configures CLI generation in this repository alongside the server SDKs. The new
cli-sdkgroup targetsVapiAI/cliin pull-request mode; Release CLI accepts an explicit version and opens a generated PR without publishing.How it works
The CLI workspace references the existing API's OpenAPI file, naming overrides and parameter overlay directly. Its OAuth/PKCE and staging-server overrides stay isolated from the other SDKs. A separate workspace is necessary because generator-level spec overrides did not reach the CLI's embedded OpenAPI in validation.
The seven existing SDK groups and their effective API configuration remain byte-for-byte unchanged. The paired CLI #21 removes the duplicated inputs, retains repository-owned docs/tests, and uses native Fern Replay for schema and command-binding customizations. Its HTTP runtime is Fernignore-protected because Replay rejects the embedded public test certificate.
Testing Steps
Risks
Merge CLI #21 before the first Release CLI invocation so the destination has its Replay baseline and Fernignore protections. Keep CLI generator 0.59.1 pinned; reconcile the protected HTTP runtime with fresh output when upgrading it.
Live OAuth acceptance, production client promotion and package-publishing setup remain release gates. This PR does not publish a package or change server SDK authentication.