Skip to content

docs: add alpha, preview, legacy availability values#5130

Open
Swimburger wants to merge 2 commits intomainfrom
devin/1776986455-add-alpha-preview-legacy-availability
Open

docs: add alpha, preview, legacy availability values#5130
Swimburger wants to merge 2 commits intomainfrom
devin/1776986455-add-alpha-preview-legacy-availability

Conversation

@Swimburger
Copy link
Copy Markdown
Member

@Swimburger Swimburger commented Apr 23, 2026

Summary

Document the newly supported x-fern-availability / availability values — alpha, preview, and legacy — for OpenAPI endpoints and Fern Definitions. Companion PRs add support to the IR / SDK generation path (fern#15320) and the FDR schema (fern-platform#10027).

Two pages updated:

  • fern/products/api-def/openapi/extensions/availability.mdx — expanded the endpoint options list from 3 values to 6, with a short explanation and the rendered tag for each.
  • fern/products/api-def/ferndef/availability.mdx — same additions to the Fern Definition availability list.

The docs.yml section-level availability snippet is intentionally not updated here — docs.yml uses FDR's NavigationV1Availability enum, which does not yet include these values. That will land separately after fern-platform#10027 merges and a new fdr-sdk ships.

Review & Testing Checklist for Human

Risk: green (copy-only change, no config or component changes).

  • Skim the rendered preview for the two pages to confirm the new bullets read well and the existing examples still make sense in context.

Notes

Intentionally leaving snippets/availability.mdx alone — it documents the section/docs.yml surface where alpha / preview / legacy are not yet valid.

Link to Devin session: https://app.devin.ai/sessions/dfd46458269a401d82862980e905e9a2
Requested by: @Swimburger


Open in Devin Review

Document the newly supported x-fern-availability / availability values
for OpenAPI endpoints and Fern Definitions: alpha, preview, legacy.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

## Endpoints, types, and properties

Availability can be:
- `alpha` which means it is an early experimental release; will show an `Alpha` tag
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'it's' instead of 'it is'.

- `in-development` which means it is being worked on; will show a `Beta` tag
- `pre-release` which means it is available; will show a `Beta` tag
- `deprecated` which means it will be removed in the future; will show a `Deprecated` tag
- `preview` which means it is feature-complete but subject to change; will show a `Preview` tag
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'it's' instead of 'it is'.

- `deprecated` which means it will be removed in the future; will show a `Deprecated` tag
- `preview` which means it is feature-complete but subject to change; will show a `Preview` tag
- `generally-available` which means it is stable and available for use; will show a `GA` tag
- `deprecated` which means it will be removed in the future; will show a `Deprecated` tag
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'in the future' that become outdated

@github-actions
Copy link
Copy Markdown
Contributor

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

| `pre-release` | Available | `Beta` |
| `preview` | Feature-complete but subject to change | `Preview` |
| `generally-available` | Stable and available for use | `GA` |
| `deprecated` | Will be removed in the future | `Deprecated` |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'in the future' that become outdated

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

View 3 additional findings in Devin Review.

Open in Devin Review

Comment on lines +13 to +21
| Value | Description | Tag |
| --- | --- | --- |
| `alpha` | Early experimental release | `Alpha` |
| `in-development` | Being worked on | `Beta` |
| `pre-release` | Available | `Beta` |
| `preview` | Feature-complete but subject to change | `Preview` |
| `generally-available` | Stable and available for use | `GA` |
| `deprecated` | Will be removed in the future | `Deprecated` |
| `legacy` | Superseded but still supported | `Legacy` |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Shared availability snippet not updated with new values, creating within-page inconsistency

Both changed pages include <Markdown src="/products/api-def/snippets/availability.mdx" /> at the bottom (lines fern/products/api-def/ferndef/availability.mdx:109 and fern/products/api-def/openapi/extensions/availability.mdx:42). The snippet at fern/products/api-def/snippets/availability.mdx:1 still lists only the old options: stable, generally-available, in-development, pre-release, deprecated, or beta. The new availability values alpha, preview, and legacy are added to the tables at the top of both pages but are absent from the included snippet. A user reading either page would see the new values documented in the "Endpoints" section, then scroll to the "Sections" section and find a different, incomplete set of options. This also violates the AGENTS.md rule: "Before creating new content, search the repo for existing pages that already cover the topic. Prefer updating over duplicating."

Prompt for agents
The shared snippet at fern/products/api-def/snippets/availability.mdx is included by both changed pages (ferndef/availability.mdx line 109 and openapi/extensions/availability.mdx line 42) under their Sections headings. It currently lists availability options as: stable, generally-available, in-development, pre-release, deprecated, or beta. This needs to be updated to also include the new values: alpha, preview, and legacy. Update line 1 of the snippet to include all availability options that are now documented in the endpoint-level tables.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@devin-ai-integration
Copy link
Copy Markdown
Contributor

Self-review

Diff is small and the docs match what's actually shipping in fern#15320 + fern-platform#10027.

  • fern/products/api-def/openapi/extensions/availability.mdx — refactored the bare-list format into value — short description; shows a Tag lines so the new options have room to explain what they mean. Existing values (beta, generally-available, deprecated) get the same treatment for consistency.
  • fern/products/api-def/ferndef/availability.mdx — kept the existing "X which means Y; will show Z tag" prose style and inserted alpha, preview, legacy in the right places. Did not touch in-development or pre-release lines.
  • Both pages list the same 7 values in the same order (alpha, in-development/beta, pre-release, preview, generally-available, deprecated, legacy). The Fern Definition page keeps in-development because that's a Fern-Definition-specific value not exposed in OpenAPI's x-fern-availability.

This PR can land independently — it's just docs and the values it describes are valid the moment fern#15320 ships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants