Repository navigation
chore: Update API specifications with fern api update (2026-10-03T00-39-54-909Z) - #1284
Merged
Merged
Conversation
# Conflicts: # fern/apis/api/openapi.json
# Conflicts: # fern/apis/api/openapi.json
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
stephenvapiai
approved these changes
Oct 3, 2026
scott-lowe-vapi
added a commit
that referenced
this pull request
Oct 6, 2026
## Summary Adds a manual trigger (`workflow_dispatch`) to **Publish Docs**, so docs.vapi.ai can be republished from the Actions tab or the CLI without merging a PR. ## Why The nightly `update-openapi` job auto-merges its spec PR with the built-in `GITHUB_TOKEN`. GitHub doesn't start other workflows from events made with that token, so **Publish Docs never runs for spec updates**. New API fields therefore don't reach the live API reference until someone merges an unrelated docs PR. Example: voice simulation latency expectations shipped on Oct 3. The spec updates that added the fields merged in #1284 (Oct 3) and #1286 (Oct 6), but the last publish ran on Oct 2, so the live Create and Update Scenario pages still don't show `latencyExpectations`. ## Change Two lines in `.github/workflows/publish-docs.yml`: - add `workflow_dispatch:` under `on:`; - widen the job's `if:` guard to accept `workflow_dispatch` as well as `push`. Without this, a manual run would show as skipped. The guard also now checks `github.ref == 'refs/heads/main'` exactly instead of `contains(...)`, so a manual run can't publish another branch. The publish steps and secrets are unchanged. ## Using it Once merged, anyone with write access can run **Actions → Publish Docs → Run workflow** on `main`, or: ```bash gh workflow run publish-docs.yml --repo VapiAI/docs --ref main ``` Merging this PR also publishes everything pending on `main`, including the latest API spec. ## Not included This makes publishing possible on demand but doesn't make it automatic after the nightly spec update. Two options for the docs owners: - merge the nightly PR with a GitHub App or bot account token instead of `GITHUB_TOKEN`, so the merge triggers Publish Docs; - or add a `schedule:` to this workflow shortly after the nightly update. ## Testing `actionlint` v1.7.7 passes with no findings, and the YAML parses with both triggers. A manual trigger can only be exercised once it's on `main`, so the first real test is a manual run after merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Update API specifications by running fern api update.