docs: declare v1beta1 stable for v1.0 and add v1.0.x compatibility row - #2270
Merged
Merged
Conversation
dosubot
Bot
added
the
size:XS
aabchoo
reviewed
Jun 22, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2270 +/- ##
==========================================
- Coverage 84.71% 84.70% -0.01%
==========================================
Files 144 144
Lines 21204 21206 +2
==========================================
Hits 17962 17962
- Misses 2161 2162 +1
- Partials 1081 1082 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
aabchoo
approved these changes
Jun 22, 2026
Prepare release documentation for the upcoming v1.0.0 release: - RELEASES.md: state that v1beta1 is the committed stable control-plane API as of v1.0.0, that v1alpha1 stays served + deprecated, and that QuotaPolicy/serviceQuota sits outside the stable surface (accepted but not yet enforced end-to-end). - site/docs/compatibility.md: add the v1.0.x compatibility row (EG v1.8.x+, Envoy v1.38.x, K8s v1.32+, Gateway API v1.5.x). Drafted with assistance from Claude (Claude Code). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Erica Hughberg <erica.sundberg.90@gmail.com>
Signed-off-by: Erica Hughberg <erica.sundberg.90@gmail.com>
missBerg
force-pushed
the
claude/pensive-moser-8b470a
branch
from
June 22, 2026 22:02
1c794db to
c1bcda0
Compare
missBerg
enabled auto-merge (squash)
June 22, 2026 22:06
yuzisun
approved these changes
Jun 22, 2026
missBerg
added a commit
to missBerg/ai-gateway
that referenced
this pull request
Jun 22, 2026
After merging upstream/main, sync version-1.0/compatibility.md to match docs/compatibility.md so the v1.0 snapshot uses the same wording landed in envoyproxy#2270 (Envoy Gateway "v1.8.1+" on the main and v1.0.x rows). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Erica Hughberg <erica.sundberg.90@gmail.com>
missBerg
added a commit
to missBerg/ai-gateway
that referenced
this pull request
Jun 23, 2026
Remove the pre-release draft comment block and inline TODOs now that each is resolved: - date set (June 23) and the real GA hero image is in place; - name v1beta1 as the stable control-plane API (1.0 ratifies it, no apiVersion bump), matching RELEASES.md/envoyproxy#2270 and the v1.0 release notes; - the feature highlights match the v1.0 release-notes surface; - the named adopters (Bloomberg, LY Corporation, Alan by Comma Soft, National Research Platform) are all publicly listed in site adopters.json. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Erica Hughberg <erica.sundberg.90@gmail.com>
missBerg
added a commit
that referenced
this pull request
Jun 23, 2026
**Description** v1.0 GA documentation for the docs site. This is the project's first GA / major-version release, so the release notes are written as a special milestone edition rather than a normal incremental delta. What's included: - **Release notes (special GA edition).** `site/src/data/releases/v1.0.json` and `site/src/pages/release-notes/v1.0.mdx`. On top of the standard sections it adds GA-specific ones: a "What 1.0 Means" intro, an API-stability commitment callout, a "Road to 1.0" journey grid, and a Support & Compatibility Policy section. The framing is that v1.0 ratifies the existing `v1beta1` control-plane API as stable under SemVer — no apiVersion change and no resource migration, so upgrading from v0.7 is a drop-in. - **Versioned 1.0 docs.** The docs are snapshotted as `versioned_docs/version-1.0` and set as the default/latest version (`versions.json` + `docusaurus.config.ts`), including the QuotaPolicy capability guide from #1947. - **Plain-markdown release body** in `release-notes/v1.0.0.md` for the GitHub release. - **Announcement blog post** under `site/blog/2026/`, with a GA announcement/OG image and credited to all nine maintainers via the Docusaurus authors mechanism. - **Wiring**: v1.0 added to the release-notes index (featured) and the v0.7 to v1.0 navigation link. Dependency versions are sourced from `go.mod` and `.envoy-version`: Go 1.26.4, Envoy Gateway v1.8.1, Envoy 1.38.1, Gateway API v1.5.1, Gateway API Inference Extension v1.0.2, MCP Go SDK v1.6.1. AI assistance: this documentation was prepared with the help of Claude Code (Claude Opus 4.8) and reviewed before submission. **Related Issues/PRs (if applicable)** Related: #1947 (QuotaPolicy capability guide), #2270 (v1beta1 stable declaration + compatibility row). **Special notes for reviewers (if applicable)** The release notes, index cards, and blog are dated June 23, 2026 — please confirm this matches the actual v1.0.0 tag date at the cut and adjust if needed. This is intended to land as part of, or immediately before, the v1.0.0 release. --------- Signed-off-by: Erica Hughberg <erica.sundberg.90@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
4 participants
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.
Description
Prepare release documentation for the upcoming v1.0.0 release. Docs-only change in two parts:
RELEASES.md— record the API stability commitment that motivates the major version bump. As of v1.0.0,v1beta1is the committed stable control-plane API and is covered by the existing "never break unless critical security" guarantee.v1alpha1remains served but deprecated and will be removed in a future release per the deprecation policy.QuotaPolicystaysv1alpha1-only and is therefore outside the stable surface; in particular itsserviceQuotafield is accepted but not yet enforced end-to-end.site/docs/compatibility.md— add thev1.0.xrow to the compatibility matrix (Envoy Gateway v1.8.x+, Envoy Proxy v1.38.x, Kubernetes v1.32+, Gateway API v1.5.x).No API, controller, or data-plane code changes.
AI usage: these docs were drafted with assistance from Claude (Claude Code) and reviewed by the author.
Related Issues/PRs (if applicable)
Special notes for reviewers (if applicable)
This is forward-looking v1.0 release-prep. The new
v1.0.xcompatibility row is markedSupportedand theRELEASES.mdwording says "as of the v1.0.0 release", even though v1.0.0 has not been tagged yet. Intent is for this to land as part of, or immediately before, the v1.0 cut rather than necessarily merging standalone today.Two items intentionally left to maintainers:
v1.0.xrow and does not change existing support statuses.serviceQuotadocs accuracy fix tracked on thedocs/quota-policy-accuracybranch is complementary to theRELEASES.mdnote added here.