# Release notes

This page describes how Ethen structures product release notes. **No product release history is documented here yet.**

## Release note structure

Future release notes will follow this format:

| Section | Content |
|---|---|
| Version / Date | Semantic version or date of release |
| Product surface | Which product area the release affects |
| Type | New feature, improvement, deprecation, fix |
| Description | What changed and how it affects users |
| Migration | Breaking changes or required configuration updates |
| Documentation | Links to relevant documentation |

## Relationship to other pages

| Page | Purpose |
|---|---|
| [Changelog](/docs/resources/changelog) | Tracks documentation content changes |
| [Release notes](/docs/resources/release-notes) | **This page** — placeholder for future product release notes |
| [Status and support](/docs/resources/status-and-support) | Current platform status and support channels |
| [FAQ](/docs/resources/faq) | Frequently asked questions |

## Coverage planned

When populated, release notes will cover:

- Gateway API version changes and endpoint deprecations
- New provider support and provider contract changes
- Model Library catalog updates
- Desktop app releases
- Approval framework and policy changes
- Enterprise control additions

## Next

Check the [platform status page](/platform) for current operational status and the [changelog](/docs/resources/changelog) for documentation content updates.