From 6061d63894f37be149a7a9acaff17b0ec6750cc2 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Mon, 17 Nov 2025 00:18:52 +0000 Subject: [PATCH 1/2] docs(asyncapi): update retry extension docs to use x-fern-retries and mark as unsupported Co-Authored-By: danny@buildwithfern.com --- .../asyncapi-pages/extensions/retry.mdx | 27 ++++++++++++------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/fern/products/api-def/asyncapi-pages/extensions/retry.mdx b/fern/products/api-def/asyncapi-pages/extensions/retry.mdx index 58cd3d997..908351329 100644 --- a/fern/products/api-def/asyncapi-pages/extensions/retry.mdx +++ b/fern/products/api-def/asyncapi-pages/extensions/retry.mdx @@ -1,19 +1,28 @@ --- title: Retry behavior -description: Configure retry behavior for operations using `x-fern-retry` extension +description: The `x-fern-retries` extension is not supported for AsyncAPI --- -Configure retry behavior for operations: + + The `x-fern-retries` extension is **not supported** for AsyncAPI WebSocket channels. Retry configuration is only available for OpenAPI HTTP endpoints. If you use this extension in your AsyncAPI specification, it will be ignored and a warning will be emitted during import. + -```yaml title="asyncapi.yml" {6-10} +For retry configuration on HTTP endpoints, use the [`x-fern-retries` extension in OpenAPI](/api-definition/openapi/extensions/retries) instead. + +## Why retries aren't supported for AsyncAPI + +AsyncAPI specifications define WebSocket channels, which are persistent, bidirectional connections. Unlike HTTP requests that follow a request-response pattern where retry logic is meaningful, WebSocket connections maintain a continuous connection where retry semantics don't apply in the same way. + +## Example (not supported) + +The following example shows the `x-fern-retries` extension in an AsyncAPI specification. This will emit a warning during import and the extension will be ignored: + +```yaml title="asyncapi.yml" {6-7} operations: sendCriticalAlert: action: send channel: $ref: '#/channels/alerts' - x-fern-retry: - max_attempts: 3 - exponential_backoff: true - initial_delay: 1000 - max_delay: 30000 -``` \ No newline at end of file + x-fern-retries: + disabled: true +``` From 9e5103fef7731330dc14be6c76891bbcc8cc90cf Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Mon, 17 Nov 2025 00:22:08 +0000 Subject: [PATCH 2/2] fix(docs): escape curly braces in CLI changelog to fix MDX parse error Co-Authored-By: danny@buildwithfern.com --- fern/products/cli-api-reference/cli-changelog/2025-11-14.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fern/products/cli-api-reference/cli-changelog/2025-11-14.mdx b/fern/products/cli-api-reference/cli-changelog/2025-11-14.mdx index ddfd6fb9d..f0bab9c02 100644 --- a/fern/products/cli-api-reference/cli-changelog/2025-11-14.mdx +++ b/fern/products/cli-api-reference/cli-changelog/2025-11-14.mdx @@ -1,5 +1,5 @@ ## 1.2.0 -**`(feat):`** Show AI example generation progress in the spinner line. When generating AI examples, the spinner displays "generating AI examples for {API name} - X/Y" to track progress without creating terminal noise. +**`(feat):`** Show AI example generation progress in the spinner line. When generating AI examples, the spinner displays "generating AI examples for \{API name\} - X/Y" to track progress without creating terminal noise. ## 1.0.5