DOCS-2987: Publish Calico Enterprise 3.24 EP1 - #2893
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!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Publishes Calico Enterprise 3.24 early preview (EP1) documentation by enabling the new version in Docusaurus and updating the 3.24-1 release notes content.
Changes:
- Added Calico Enterprise docs version
3.24-1to the Docusaurus version configuration (labeled as early preview). - Updated Calico Enterprise
3.24-1release notes structure and content, including upgrade guidance and release details.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docusaurus.config.js | Exposes Calico Enterprise 3.24-1 as an “early preview” version and includes it in the published versions list. |
| calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx | Updates 3.24 release notes sections (enhancements, upgrading, breaking changes, release details). |
| {/* ## Technology Preview features */} | ||
|
|
||
| ## Upgrade notes | ||
| {/* ### Known issues */} |
| ### Calico Enterprise 3.24.0-1.0 (early preview) | ||
|
|
||
| January xx, 2024 | ||
| July 30, 2025 |
Run make version/autogen/3.24-1 to replace the placeholder component pins in version-3.24-1/releases.json with the real values from the release-calient-v3.24-1 branch of calico-private. This sets tigera-operator to v1.43.0, the Calico base to v3.32, and applies the 3.24 image-name consolidation and component version corrections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… 1.43 Regenerate version-3.24-1/reference/installation/_api.mdx from the operator 1.43 CRD API. The GA v1.43.0 tag is not yet published in tigera/operator, so the reference is generated from the release-v1.43 branch, which is the line that becomes v1.43.0; regenerate against the tag once it is cut. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bump envoyVersion in version-3.24-1/variables.js from 1.8.0 to 1.8.2, matching the github.com/envoyproxy/gateway pin on the release-calient-v3.24-1 branch of calico-private. This is the version rendered in the Calico Ingress Gateway docs. openSourceVersion needs no change; it derives from releases.json and now resolves to 3.32. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…d next Remove the compliance reporting feature documentation from Calico Enterprise next and version-3.24-1, since the feature has been removed from the web console and has no shipped replacement. - Delete the compliance guide pages, the compliance-reports reference pages, and the GlobalReport resource page. - Reword the compliance index into a Security landing and relabel the sidebar category to Security; keep the WireGuard, HTTP proxy, and Istio Ambient pages in place at their current paths. - Remove compliance cross-links, the feature-matrix and RBAC rows, reference cards, the get-started Compliance Reports section, and the compliance troubleshooting section. - Remove install-time compliance references from the Helm reference and tigerastatus, and exclude Compliance types from the generated operator API reference (ignoreTypes) so regeneration keeps them out. - Add a plain removal entry to the release notes with no successor named. Across all products and versions, remove the sentence about a coming replacement from every surviving compliance deprecation notice: Calico Enterprise 3.20-2 through 3.23-2, and Calico Cloud next, 22-2, and 23-2. Calico Cloud compliance pages are kept; only the notices change. releases.json is unchanged; the compliance-benchmarker component still ships. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…release notes Demote the Calico Ingress Gateway breaking-change heading to a subsection so it nests under Upgrade notes, and drop the bold lead-in from the first migration step. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Set the 3.24.0-1.0 release-details date to July 31, 2026, and remove the dead anchor link on the Known issues reference in the Upgrading intro while keeping the text. 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
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.
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: