VapiAI / docs

Vapi docs
1 stars 0 forks source link

:herb: :sparkles: [Scheduled] Upgrade Fern CLI #1

Closed fern-api[bot] closed 2 weeks ago

fern-api[bot] commented 1 month ago

Upgrading from 0.42.14 to 0.43.7 - Changelog

    0.43.7
  • fix: The `valid-markdown` rule has been updated to try and parse the markdown file into a valid AST. If the file fails to parse, `fern check` will log an error as well as the path to the markdown.
  • 0.43.6
  • fix: The OpenAPI importer now appropriately brings in responses that are under the `text/event-stream` Content-Type if your endpoint is annotated with `x-fern-streaming`. If your endpoint is not annotated with `x-fern-streaming`, then the response will be ignored.
  • 0.43.5
  • fix: If you use the `x-fern-streaming` extension and want to provide different descriptions for the streaming endpoint, then you can now specify `streaming-description`. ```yml openapi.yml x-fern-streaming: stream-condition: $request.stream stream-description: The streaming version of this endpoint returns a series of chunks ... response: $ref: #/components/schemas/Response stream-response: $ref: #/components/schemas/ResponseChunk ```
  • 0.43.4
  • fix: The OpenAPI parser now respects the content type in your OpenAPI spec, instead of always sending `application/json`. With this upgrade, your SDKs will also start to send the correct content type.
  • 0.43.3
  • chore: The CLI now passes in the API definition ID once again, this is necessary so that generated snippet templates may reference schemas within the API. This was a regression that was recently introduced.
  • 4 additional updates, see more
    0.43.2
  • fix: The CLI now prints which API cannot be registered if `fern generate --docs` fails.
  • 0.43.1
  • feat: The CLI now supports running OpenAPI generator 0.1.0 with IR version 53.
  • 0.43.0
  • feat: The CLI now recognizes the fern-php-sdk generator.
  • 0.42.15
  • internal: The documentation resolver now approrpiately creates a unique identifier for changelog sections. Previously, if you had multiple changelogs within the same section, despite their title and slug being different, they would be treated as the same section since the ID only took into account the parents' slug, appended the word "changelog" and that was all. As a result previously all changelogs within the same section would get highlighted when one was selected, now only the selected changelog is highlighted.