DOCS-3009: Add technology preview tables to the Calico Open Source release notes - #2924
Merged
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds “Feature status” tables to Calico Open Source 3.30–3.32 release notes so readers can quickly see which formerly–tech preview features remained TP, became GA, or were unavailable across those releases (and adds a GA announcement for Calico Ingress Gateway in 3.31).
Changes:
- Added a “Feature status” section with a per-release status table to the 3.30, 3.31, and 3.32 release notes (with the appropriate release window/columns per version).
- Added an explicit “Calico Ingress Gateway is now generally available” callout section to the 3.31 release notes.
- Included a selector-scoped Felix configuration row in the 3.32 table, linking directly to the appropriate in-page anchor.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| calico_versioned_docs/version-3.32/release-notes/index.mdx | Adds the widest status table (3.30–3.32), including newer TP items and a verified anchor link for selector-scoped Felix configuration. |
| calico_versioned_docs/version-3.31/release-notes/index.mdx | Adds the 3.30–3.31 status table and a new GA announcement section for Calico Ingress Gateway. |
| calico_versioned_docs/version-3.30/release-notes/index.mdx | Adds the single-column (3.30-only) status table for TP features introduced/present in 3.30. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (3)
calico_versioned_docs/version-3.32/release-notes/index.mdx:89
- The intro text for this section omits the standard warning that tech preview features are for evaluation only and not supported for production use. The release notes template (calico-enterprise/release-notes/_template.mdx:70) includes that disclaimer; without it, readers may assume TP features are production-supported.
This table shows the status of features that were in tech preview at any point in the releases covered here.
Tech preview features can change significantly before they become generally available.
calico_versioned_docs/version-3.31/release-notes/index.mdx:180
- The intro text for this section omits the standard warning that tech preview features are for evaluation only and not supported for production use. The release notes template (calico-enterprise/release-notes/_template.mdx:70) includes that disclaimer; without it, readers may assume TP features are production-supported.
This table shows the status of features that were in tech preview at any point in the releases covered here.
Tech preview features can change significantly before they become generally available.
calico_versioned_docs/version-3.30/release-notes/index.mdx:154
- The intro text for this section omits the standard warning that tech preview features are for evaluation only and not supported for production use. The release notes template (calico-enterprise/release-notes/_template.mdx:70) includes that disclaimer; without it, readers may assume TP features are production-supported.
This table shows the status of features that are in tech preview in this release.
Tech preview features can change significantly before they become generally available.
ctauchen
force-pushed
the
tp-search
branch
2 times, most recently
from
August 17, 2026 11:20
aab6f43 to
8667e57
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (6)
calico_versioned_docs/version-3.32/release-notes/index.mdx:100
- In this lifecycle table, “–” appears to mean the feature was not yet introduced in that release (rather than generally “not available”). Tweaking the legend wording would make the table more precise.
TP = tech preview, GA = generally available, – = not available in that release.
calico_versioned_docs/version-3.31/release-notes/index.mdx:188
- In this lifecycle table, “–” is used for releases prior to a feature being introduced. Updating the legend to say “not yet introduced” would be more precise than “not available”.
TP = tech preview, GA = generally available, – = not available in that release.
calico_versioned_docs/version-3.30/release-notes/index.mdx:162
- The table uses “–” for releases before a feature existed. Consider updating the legend to “not yet introduced” (and defining GA, since the preceding sentence uses the GA abbreviation).
TP = tech preview, – = not available in that release.
calico_versioned_docs/version-3.32/release-notes/index.mdx:89
- To keep tech preview messaging consistent across Calico OSS docs, consider using the standard sentence used on tech preview feature pages (for example, calico_versioned_docs/version-3.32/observability/view-flow-logs.mdx:13).
This issue also appears on line 100 of the same file.
Tech preview features can change significantly before they become generally available.
calico_versioned_docs/version-3.31/release-notes/index.mdx:180
- To keep tech preview messaging consistent across Calico OSS docs, consider using the standard sentence used on tech preview feature pages (for example, calico_versioned_docs/version-3.31/observability/flow-logs-api.mdx).
This issue also appears on line 188 of the same file.
Tech preview features can change significantly before they become generally available.
calico_versioned_docs/version-3.30/release-notes/index.mdx:154
- To keep tech preview messaging consistent across Calico OSS docs, consider using the standard sentence used on tech preview feature pages (for example, calico_versioned_docs/version-3.30/networking/gateway-api.mdx).
This issue also appears on line 162 of the same file.
Tech preview features can change significantly before they become generally available.
Copilot stopped reviewing on behalf of
ctauchen due to an error
August 17, 2026 14:52
Add a Technology preview features section to the Calico Open Source 3.30, 3.31, and 3.32 release notes. Each table covers a rolling window of three releases and lists every feature that was in technology preview at any point in that window. The heading, placement, and wording follow the release notes template. The flow logs API and Whisker share one row, because the two ship together and have held the same status in every release. The Feature column names each feature in plain text. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…in 3.31 Add a Calico Ingress Gateway section to the 3.31 new features. The feature page dropped its technology preview note in 3.31, but the release notes never recorded the change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replace the short wording about features changing before GA with the disclaimer from the release notes template, which states that technology preview features are for evaluation and feedback only and are not supported for production use. This keeps the open source tables consistent with the Calico Enterprise tables in tigera#2925. Keep the sentence that says what the table covers, because the table spans three releases and includes features that have since reached GA, so the template's opening sentence does not fit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ctauchen
changed the title
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
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.
The release notes announce a feature when it enters technology preview, but nothing records what happened to it afterwards. This adds a Technology preview features section to the Calico Open Source 3.30, 3.31, and 3.32 release notes, following the release notes template. Each table covers a rolling window of three releases and lists every feature that was in technology preview at any point in that window.
Changes:
Deploy preview: https://deploy-preview-2924--tigera.netlify.app/calico/latest/release-notes
DOCS-3009: https://tigera.atlassian.net/browse/DOCS-3009