Repository navigation
DOC-3290: document opt-in Zot certificate rotation for the management appliances - #12173
Merged
Merged
Conversation
* DOC-3205 - Patch release notes for 4.10.16 (#11956) * DOC-3205 - Patch release notes for 4.10.x Add the Bug Fixes section for the 4.10.x patch released on September 10, plus the placeholder Edge Compatibility Matrix and CLI Tools rows. The patch version and the CanvOS and Palette CLI versions are pending. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs: patch release 4.10.16 --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Linus Bourque <linus@spectrocloud.com> * docs: mention PaletteAI Inference Launchpad (#11960) The AI Workloads landing page already routed readers to PaletteAI for a full AI platform experience, but nothing under docs-content linked to the PaletteAI Inference Launchpad collection, which left the navbar tab as its only entry point. Add a one-sentence off-ramp that leads with what the appliance does for the reader and names the product in its closing link. Add a matching third bullet to the Resources list. Link with an absolute path rather than a relative Markdown link, because PaletteAI Inference Launchpad is a separate Docusaurus docs collection and relative links cannot resolve across collections. Expand LLM on first use, since the abbreviation is absent from the acronym-no-expand Vale exemption list and the Resources bullet relies on the expansion appearing first. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> * chore: bump @argos-ci/core, @argos-ci/cli and @argos-ci/playwright (#11962) * chore: bump @argos-ci/core, @argos-ci/cli and @argos-ci/playwright Bumps [@argos-ci/core](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core) to 6.2.3 and updates ancestor dependencies [@argos-ci/core](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core), [@argos-ci/cli](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core) and [@argos-ci/playwright](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/playwright). These dependencies need to be updated together. Updates `@argos-ci/core` from 6.1.0 to 6.2.3 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/core@6.2.3/packages/core) Updates `@argos-ci/cli` from 5.0.4 to 5.1.3 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/cli@5.1.3/packages/core) Updates `@argos-ci/playwright` from 6.4.2 to 7.5.0 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/playwright/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/playwright@7.5.0/packages/playwright) --- updated-dependencies: - dependency-name: "@argos-ci/core" dependency-version: 6.2.3 dependency-type: indirect - dependency-name: "@argos-ci/cli" dependency-version: 5.1.3 dependency-type: direct:development - dependency-name: "@argos-ci/playwright" dependency-version: 7.5.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> * chore(ci): trigger CI again --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Linus Bourque <linus@spectrocloud.com> * chore: make patch release notes re-runnable on the day a patch ships (#11967) The values `make generate-patch-release-notes` records are mostly settled on the day a patch ships, not on the day the ticket arrives. Every one of them is now asked for again on each run, proposed with a default so confirming costs one keystroke, and the rows an earlier run wrote for a value that has since changed are removed rather than left to be tidied by hand. - Candidate issues are resolved from PATCH_CANDIDATE_ISSUES, the candidates link, the issue keys written into the description, or the prompt, so a ticket that names a single issue or only describes the patch no longer stops the run. A ticket that names none scaffolds the body with a BODY PENDING marker, and a later run leaves a hand-written body exactly as written. - The release date takes a manual override, because the issue tracker is not a reliable record of when a patch shipped. - The version is seeded from the ticket summary, which names the real version, ahead of the fixVersion placeholder in the candidates query. - CanvOS and Palette CLI versions can be given by hand, with `same` for a component this patch did not bump. - Confirming that a component did not move removes the rows and release notes section an earlier run wrote for it. - The candidate list is recorded in a marker, so a re-run reports which tickets were added and dropped, and tells Super to remove the dropped ones. Rows are only removed when the component question was actually answered, and an unattended re-run keeps the version and date the section already records, so the comment-triggered Update Patch Release Notes workflow cannot revert a confirmed section or delete its component rows. Also fixes a pre-existing bug that a live run exposed. The component version comparison read the first data row of the table, but rows are ordered newest first across every release train, so 4.10.16 sits above 4.9.53. A 4.9 patch was compared against the 4.10 row, reporting components as moved when they had not and resolving "the version already documented" to a newer train's value. The baseline is now the newest row in the patch's own major.minor train. The Palette CLI install page is excluded, because it documents the version a reader should install rather than one release's version, so a pending marker there is repaired from the newest version in the CLI Tools table. The train is derived with parameter expansion rather than a capture group, because BASH_REMATCH came back empty under the bash 3.2 that ships with macOS while working under the bash 5 on the CI runner, which had the train resolve silently to empty and read the wrong row. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> * DOC-3195: component update script updates (#11957) * DOC-3195: component update script updates * option to change base branch * updating templates * appliance and kubernetes logic * adding deprecations to template * adding ben's suggestion in --------- Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> * exclude two node clusters from systemd extension support (#11961) * exclude two node clusters from systemd extension support * remove BUNDLE_K8S_AND_AGENT_PROVIDER data remove BUNDLE_K8S_AND_AGENT_PROVIDER data as the default value is true * ci: auto-formatting prettier issues * remove trailing slash * remove the flag details * ci: auto-formatting prettier issues --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Linus Bourque <linus@spectrocloud.com> * docs: add component updates for DOC-3191 (#11976) * docs: add component updates for DOC-3191 * docs: update component updates * removing deprecations and pack notes headers from component updates --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Linus C Bourque <linus@spectrocloud.com> * DOC-3112 - Mark K3s deprecated for virtual clusters (#11942) * DOC-3112: mark K3s deprecated for Palette Virtual Clusters Update Palette Virtual Cluster docs to reflect that K3s is deprecated as a virtual cluster distribution. Kubernetes is now described as the default, with a warning admonition covering both content pages. The PDE tutorial and troubleshooting scenario carry matching updates, and a Deprecations and Removals entry backfills the 4.10.13 release notes citing the original 4.8.0 deprecation. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * update screenshot with distributions * Optimised images with calibre/image-actions --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * PE-9510: Document Amazon ECR provider registry for Edge clusters (#11974) * PE-9510: ecr-edge provider registry * PE-9510: ecr-edge provider registry * adjustments as per Kurt's suggestions * chore: bump nanoid from 3.3.16 to 3.3.19 (#11984) Bumps [nanoid](https://github.com/ai/nanoid) from 3.3.16 to 3.3.19. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](ai/nanoid@3.3.16...3.3.19) --- updated-dependencies: - dependency-name: nanoid dependency-version: 3.3.19 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * docs: propose a clearer glossary definition of Appliance (#11980) * docs: propose a clearer glossary definition of Appliance The previous definition described the appliance as "a single server," which conflated the machine with the software running on it. Readers who asked what "PAIIL appliance" refers to came away from the glossary entry more confused than before, because it named hardware first and the stack second. The new definition says the appliance is software, not hardware, in the opening clause, lists the pre-integrated layers, and states the relationship to the machine: you provide the server, it becomes a node, and you install the appliance on it. It also drops the claim that the appliance ships as a bootable image, which the two-stage slim ISO and content bundle install does not match. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs: port the Appliance definition to the 1.0.x glossary The version-1.0.x cut carried the same "a single server that ships as a bootable image" wording as master, so a reader on the 1.0.x docs would still hit the hardware-versus-software confusion the new definition resolves. Both glossaries now carry identical entries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> * DOC-3214: VMO Direct Mode and Connect Button (#11983) * DOC-3214: VMO Direct Mode and Connect Button * adjusting as per Sheldon's comment * removing future references * docs: document connect to coding agents (#11987) Replace the TLS-bypass and publicly-trusted-certificate guidance in the four coding agent how-tos with the platform CA download the connect panel now offers. Add a shared partial for that download step and per-agent trust variables: NODE_EXTRA_CA_CERTS for Claude Code and OpenCode, CODEX_CA_CERTIFICATE for Codex, and the operating system trust store for Cursor. Align every snippet with the console, including the launchpad provider name, the LAUNCHPAD_API_KEY environment key, wire_api responses, and the seeded gpt and Claude tier aliases. Document Cursor's private-network limit in the Cursor how-to and reference rather than as a known issue, because Cursor sends model requests from its own cloud and no client-side step changes that. Drop the Cursor admin API alias procedure and point operators at a client's Routing tab and Cursor's Add model control instead. Record that every new API token requires an expiration date up to 366 days ahead, and add the expiring soon state to the token state lists. Remove the Anthropic model alias known issue, and document the seven seeded alias prefixes with the inheritance rule that replaced it. Flag four product-behavior questions for SME review as inline comments. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs: add optional "that" style rule (#11988) * docs: add optional "that" style rule Adds a new '## Optional "That"' section to Grammar Guidance, covering the rule to keep the conjunction "that" when it introduces a subordinate clause even where it can be dropped. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs: add TOC entry for optional "that" Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: brent-eritou <brent.eritou@spectrocloud.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Santhosh <santoshdaivajna@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: vault-token-factory-spectrocloud[bot] <133815545+vault-token-factory-spectrocloud[bot]@users.noreply.github.com> Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com>
…via #11991); restore ancestry
…nto pem-11997-api-authz-breaking-change
…e-land via reviewed PR) (#11997)
…1994) * PEM-11996: release note for pull secret configured-by attribution * PEM-11996: reword pull secret attribution note per review * chore(ci): trigger CI again
* PE-9526: Local UI Expired password steps/release ntoe * chore(ci): trigger CI again * chore(ci): trigger CI again
…API (#11998) * PEM-11997: 4.10.a breaking change - enforced authorization checks on four APIs * additional info added for permissions * docs: clarify PEM-11997 breaking-change wording per review
…rning (#11995) * PE-9524 / PEM-11994: 4.10.a upgrade note for DHI image pull secret warning * chore(ci): trigger CI again * PE-9524 / PEM-11994: add DHI pull-secret upgrade note to config pages * docs: consolidate DHI pull-secret warning into shared partial, reframe release note (PE-9524/PEM-11994) * chore(ci): trigger CI again
* PCP-7615: update version and release notes pending PM response to CAPI core question Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * PCP-7615: add CAPI core and generalize section Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * PCP-7615: sync CAPI versions to PM table Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
* PEM-11991: Copy from Control Plane Pool day-2 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Qualify Copy from Control Plane Pool note Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* PEM-11995: Remove EKS Hybrid Nodes docs Deletes the eks-hybrid-nodes/ directory now that hybrid node configuration is disabled in the UI and API. Adds redirects for the eight removed URLs to /clusters/public-cloud/aws/eks/, prunes hybrid references from add-aws-accounts, imported-clusters, and known-issues, moves the announcements row from Deprecations to Removals, and adds the 4.10.a release note. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * PEM-11995: Move EKS Hybrid Nodes docs to deprecated/ Preserves the removed eks-hybrid-nodes/ pages under docs/deprecated/ instead of deleting them, so the content remains available in the repo for future reference. Docusaurus serves only docs/docs-content/, so these pages are off-site; the redirects added earlier still handle the old URLs on the live site. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
* updates as per Edge team * final edits * Update docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images/build-hadron-image.md Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com> --------- Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com>
) * PEM-12052: mongo helm scheduling * updating observability.enabled settings * Update docs/docs-content/vertex/install-palette-vertex/install-on-kubernetes/vertex-helm-ref.md Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com> * ci: auto-formatting prettier issues * as per Kurt's suggestions --------- Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* DOC-3019: VMMA VDDK 9 * adding release note
…12018) * PEM-11992: scaffold export-only metrics observability docs (Palette + VerteX) * adjustments after Varun provided more details * updated info based on Varun's demo video * additional items * adjusting scope since EC isn't supported for this * removing left over comment * adding line to Features for Release Notes * added Kurt's suggestions
* adding breaking change * DOC-3230: add OIDC callback URL registration page Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * DOC-3230: add security notice for callback URL validation Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * DOC-3230: note macro exception to automatic callback URL registration Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* first draft Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * reorder: concept before task Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * align content with epic; add cluster template permissions Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * prefer "after" over "once" in create page Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * conform Validate section to house style Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * strip author notes; tighten Next Steps wording Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * add 4.10.a release note for cluster attach feature Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * mention Terraform provider in release note bullet Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* PE-9521 - Agent version in UI Point users at the Stylus Version column on the Edge Hosts page instead of the API call for identifying the latest Palette agent version. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * PE-9521 - Fix agent casing and icon wording Lowercase "Palette agent" in step 5 and use "warning icon" consistently in step 4. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Trigger CI * PE-9521 - Update inbound links for renamed section Point troubleshooting and known-issues links at the renamed heading "Identify the Latest Palette Agent Version". Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs: Apply batched suggestions from code review Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com>
benradstone
reviewed
Oct 12, 2026
Contributor
|
✅ CI checks passed for commit bcf17aa. |
…ch step 37 to the new installer
Linus-SpectroCloud
added
the
do-not-merge/work-in-progress
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
|
✅ CI checks passed for commit df5890b. |
Contributor
|
✅ CI checks passed for commit 0817d7a. |
Linus-SpectroCloud
added
auto-backport
Contributor
|
✅ CI checks passed for commit f7d3ac1. |
11 of 13 tasks
Contributor
|
✅ CI checks passed for commit 080ddd6. |
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
vault-token-factory-spectrocloud Bot
added a commit
that referenced
this pull request
Oct 15, 2026
… appliances (#12173) (#12236) * fix: Release 4.10.a * PEM-11997: 4.10.a breaking change - enforced authorization checks on four APIs * Sync master into docs rel 4 10 a (#11991) * DOC-3205 - Patch release notes for 4.10.16 (#11956) * DOC-3205 - Patch release notes for 4.10.x Add the Bug Fixes section for the 4.10.x patch released on September 10, plus the placeholder Edge Compatibility Matrix and CLI Tools rows. The patch version and the CanvOS and Palette CLI versions are pending. * docs: patch release 4.10.16 --------- * docs: mention PaletteAI Inference Launchpad (#11960) The AI Workloads landing page already routed readers to PaletteAI for a full AI platform experience, but nothing under docs-content linked to the PaletteAI Inference Launchpad collection, which left the navbar tab as its only entry point. Add a one-sentence off-ramp that leads with what the appliance does for the reader and names the product in its closing link. Add a matching third bullet to the Resources list. Link with an absolute path rather than a relative Markdown link, because PaletteAI Inference Launchpad is a separate Docusaurus docs collection and relative links cannot resolve across collections. Expand LLM on first use, since the abbreviation is absent from the acronym-no-expand Vale exemption list and the Resources bullet relies on the expansion appearing first. * chore: bump @argos-ci/core, @argos-ci/cli and @argos-ci/playwright (#11962) * chore: bump @argos-ci/core, @argos-ci/cli and @argos-ci/playwright Bumps [@argos-ci/core](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core) to 6.2.3 and updates ancestor dependencies [@argos-ci/core](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core), [@argos-ci/cli](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/core) and [@argos-ci/playwright](https://github.com/argos-ci/argos-javascript/tree/HEAD/packages/playwright). These dependencies need to be updated together. Updates `@argos-ci/core` from 6.1.0 to 6.2.3 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/core@6.2.3/packages/core) Updates `@argos-ci/cli` from 5.0.4 to 5.1.3 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/cli@5.1.3/packages/core) Updates `@argos-ci/playwright` from 6.4.2 to 7.5.0 - [Release notes](https://github.com/argos-ci/argos-javascript/releases) - [Changelog](https://github.com/argos-ci/argos-javascript/blob/main/packages/playwright/CHANGELOG.md) - [Commits](https://github.com/argos-ci/argos-javascript/commits/@argos-ci/playwright@7.5.0/packages/playwright) --- updated-dependencies: - dependency-name: "@argos-ci/core" dependency-version: 6.2.3 dependency-type: indirect - dependency-name: "@argos-ci/cli" dependency-version: 5.1.3 dependency-type: direct:development - dependency-name: "@argos-ci/playwright" dependency-version: 7.5.0 dependency-type: direct:development ... * chore(ci): trigger CI again --------- * chore: make patch release notes re-runnable on the day a patch ships (#11967) The values `make generate-patch-release-notes` records are mostly settled on the day a patch ships, not on the day the ticket arrives. Every one of them is now asked for again on each run, proposed with a default so confirming costs one keystroke, and the rows an earlier run wrote for a value that has since changed are removed rather than left to be tidied by hand. - Candidate issues are resolved from PATCH_CANDIDATE_ISSUES, the candidates link, the issue keys written into the description, or the prompt, so a ticket that names a single issue or only describes the patch no longer stops the run. A ticket that names none scaffolds the body with a BODY PENDING marker, and a later run leaves a hand-written body exactly as written. - The release date takes a manual override, because the issue tracker is not a reliable record of when a patch shipped. - The version is seeded from the ticket summary, which names the real version, ahead of the fixVersion placeholder in the candidates query. - CanvOS and Palette CLI versions can be given by hand, with `same` for a component this patch did not bump. - Confirming that a component did not move removes the rows and release notes section an earlier run wrote for it. - The candidate list is recorded in a marker, so a re-run reports which tickets were added and dropped, and tells Super to remove the dropped ones. Rows are only removed when the component question was actually answered, and an unattended re-run keeps the version and date the section already records, so the comment-triggered Update Patch Release Notes workflow cannot revert a confirmed section or delete its component rows. Also fixes a pre-existing bug that a live run exposed. The component version comparison read the first data row of the table, but rows are ordered newest first across every release train, so 4.10.16 sits above 4.9.53. A 4.9 patch was compared against the 4.10 row, reporting components as moved when they had not and resolving "the version already documented" to a newer train's value. The baseline is now the newest row in the patch's own major.minor train. The Palette CLI install page is excluded, because it documents the version a reader should install rather than one release's version, so a pending marker there is repaired from the newest version in the CLI Tools table. The train is derived with parameter expansion rather than a capture group, because BASH_REMATCH came back empty under the bash 3.2 that ships with macOS while working under the bash 5 on the CI runner, which had the train resolve silently to empty and read the wrong row. * DOC-3195: component update script updates (#11957) * DOC-3195: component update script updates * option to change base branch * updating templates * appliance and kubernetes logic * adding deprecations to template * adding ben's suggestion in --------- * exclude two node clusters from systemd extension support (#11961) * exclude two node clusters from systemd extension support * remove BUNDLE_K8S_AND_AGENT_PROVIDER data remove BUNDLE_K8S_AND_AGENT_PROVIDER data as the default value is true * ci: auto-formatting prettier issues * remove trailing slash * remove the flag details * ci: auto-formatting prettier issues --------- * docs: add component updates for DOC-3191 (#11976) * docs: add component updates for DOC-3191 * docs: update component updates * removing deprecations and pack notes headers from component updates --------- * DOC-3112 - Mark K3s deprecated for virtual clusters (#11942) * DOC-3112: mark K3s deprecated for Palette Virtual Clusters Update Palette Virtual Cluster docs to reflect that K3s is deprecated as a virtual cluster distribution. Kubernetes is now described as the default, with a warning admonition covering both content pages. The PDE tutorial and troubleshooting scenario carry matching updates, and a Deprecations and Removals entry backfills the 4.10.13 release notes citing the original 4.8.0 deprecation. * update screenshot with distributions * Optimised images with calibre/image-actions --------- * PE-9510: Document Amazon ECR provider registry for Edge clusters (#11974) * PE-9510: ecr-edge provider registry * PE-9510: ecr-edge provider registry * adjustments as per Kurt's suggestions * chore: bump nanoid from 3.3.16 to 3.3.19 (#11984) Bumps [nanoid](https://github.com/ai/nanoid) from 3.3.16 to 3.3.19. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](ai/nanoid@3.3.16...3.3.19) --- updated-dependencies: - dependency-name: nanoid dependency-version: 3.3.19 dependency-type: indirect ... * docs: propose a clearer glossary definition of Appliance (#11980) * docs: propose a clearer glossary definition of Appliance The previous definition described the appliance as "a single server," which conflated the machine with the software running on it. Readers who asked what "PAIIL appliance" refers to came away from the glossary entry more confused than before, because it named hardware first and the stack second. The new definition says the appliance is software, not hardware, in the opening clause, lists the pre-integrated layers, and states the relationship to the machine: you provide the server, it becomes a node, and you install the appliance on it. It also drops the claim that the appliance ships as a bootable image, which the two-stage slim ISO and content bundle install does not match. * docs: port the Appliance definition to the 1.0.x glossary The version-1.0.x cut carried the same "a single server that ships as a bootable image" wording as master, so a reader on the 1.0.x docs would still hit the hardware-versus-software confusion the new definition resolves. Both glossaries now carry identical entries. --------- * DOC-3214: VMO Direct Mode and Connect Button (#11983) * DOC-3214: VMO Direct Mode and Connect Button * adjusting as per Sheldon's comment * removing future references * docs: document connect to coding agents (#11987) Replace the TLS-bypass and publicly-trusted-certificate guidance in the four coding agent how-tos with the platform CA download the connect panel now offers. Add a shared partial for that download step and per-agent trust variables: NODE_EXTRA_CA_CERTS for Claude Code and OpenCode, CODEX_CA_CERTIFICATE for Codex, and the operating system trust store for Cursor. Align every snippet with the console, including the launchpad provider name, the LAUNCHPAD_API_KEY environment key, wire_api responses, and the seeded gpt and Claude tier aliases. Document Cursor's private-network limit in the Cursor how-to and reference rather than as a known issue, because Cursor sends model requests from its own cloud and no client-side step changes that. Drop the Cursor admin API alias procedure and point operators at a client's Routing tab and Cursor's Add model control instead. Record that every new API token requires an expiration date up to 366 days ahead, and add the expiring soon state to the token state lists. Remove the Anthropic model alias known issue, and document the seven seeded alias prefixes with the inheritance rule that replaced it. Flag four product-behavior questions for SME review as inline comments. * docs: add optional "that" style rule (#11988) * docs: add optional "that" style rule Adds a new '## Optional "That"' section to Grammar Guidance, covering the rule to keep the conjunction "that" when it introduces a subordinate clause even where it can be dropped. * docs: add TOC entry for optional "that" --------- --------- * chore(ci): trigger CI again * Remove PEM-11997 breaking-change entry (merged without review; will re-land via reviewed PR) (#11997) * PEM-11996: release note for pull secret configured-by attribution (#11994) * PEM-11996: release note for pull secret configured-by attribution * PEM-11996: reword pull secret attribution note per review * chore(ci): trigger CI again * PVM-1182 / DOC-3019: document Broadcom VDDK download restriction (#11993) * PVM-1182 / DOC-3019: document Broadcom VDDK download restriction for VM migration * chore(ci): trigger CI again * PE-9526: Local UI Expired password steps/release note (#11989) * PE-9526: Local UI Expired password steps/release ntoe * chore(ci): trigger CI again * chore(ci): trigger CI again * PE-9526: adding additional content (#11999) * PEM-11997: 4.10.a breaking change - enforced authorization checks on API (#11998) * PEM-11997: 4.10.a breaking change - enforced authorization checks on four APIs * additional info added for permissions * docs: clarify PEM-11997 breaking-change wording per review * PE-9524 / PEM-11994: 4.10.a upgrade note for DHI image pull secret warning (#11995) * PE-9524 / PEM-11994: 4.10.a upgrade note for DHI image pull secret warning * chore(ci): trigger CI again * PE-9524 / PEM-11994: add DHI pull-secret upgrade note to config pages * docs: consolidate DHI pull-secret warning into shared partial, reframe release note (PE-9524/PEM-11994) * chore(ci): trigger CI again * PCP-7615: Update CAPI provider versions (#12011) * PCP-7615: update version and release notes pending PM response to CAPI core question * PCP-7615: add CAPI core and generalize section * PCP-7615: sync CAPI versions to PM table --------- * PVM-1183: NAD VLAN Filtering (4.10.a) * updating vmo-pack-parameters * minor adjustments * PEM-11991 - Copy from Control Plane Pool day-2 (#12021) * PEM-11991: Copy from Control Plane Pool day-2 * Qualify Copy from Control Plane Pool note * ci: auto-formatting prettier issues --------- * PEM-11995: Remove EKS Hybrid Nodes docs (#12024) * PEM-11995: Remove EKS Hybrid Nodes docs Deletes the eks-hybrid-nodes/ directory now that hybrid node configuration is disabled in the UI and API. Adds redirects for the eight removed URLs to /clusters/public-cloud/aws/eks/, prunes hybrid references from add-aws-accounts, imported-clusters, and known-issues, moves the announcements row from Deprecations to Removals, and adds the 4.10.a release note. * PEM-11995: Move EKS Hybrid Nodes docs to deprecated/ Preserves the removed eks-hybrid-nodes/ pages under docs/deprecated/ instead of deleting them, so the content remains available in the repo for future reference. Docusaurus serves only docs/docs-content/, so these pages are off-site; the redirects added earlier still handle the old URLs on the live site. --------- * PE-9321: Rook Cephnfs known issue (#12037) * PE-9527: Hadron Connected Edge (#12041) * updates as per Edge team * final edits * Update docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images/build-hadron-image.md --------- * PEM-12052: MongoDB Helm scheduling + observability.enabled field (#12038) * PEM-12052: mongo helm scheduling * updating observability.enabled settings * Update docs/docs-content/vertex/install-palette-vertex/install-on-kubernetes/vertex-helm-ref.md * ci: auto-formatting prettier issues * as per Kurt's suggestions --------- * DOC-3019: VMMA VDDK 9 (#12043) * DOC-3019: VMMA VDDK 9 * adding release note * PEM-11992: export-only metrics observability docs (Palette/VerteX) (#12018) * PEM-11992: scaffold export-only metrics observability docs (Palette + VerteX) * adjustments after Varun provided more details * updated info based on Varun's demo video * additional items * adjusting scope since EC isn't supported for this * removing left over comment * adding line to Features for Release Notes * added Kurt's suggestions * DOC-3230 - OIDC callback URL allowlist (#12054) * adding breaking change * DOC-3230: add OIDC callback URL registration page * DOC-3230: add security notice for callback URL validation * DOC-3230: note macro exception to automatic callback URL registration --------- * PEM-11993: Attach existing cluster to template (#12045) * first draft * reorder: concept before task * align content with epic; add cluster template permissions * prefer "after" over "once" in create page * conform Validate section to house style * strip author notes; tighten Next Steps wording * add 4.10.a release note for cluster attach feature * mention Terraform provider in release note bullet * ci: auto-formatting prettier issues --------- * PE-9521 - Agent version in UI (#12046) * PE-9521 - Agent version in UI Point users at the Stylus Version column on the Edge Hosts page instead of the API call for identifying the latest Palette agent version. * PE-9521 - Fix agent casing and icon wording Lowercase "Palette agent" in step 5 and use "warning icon" consistently in step 4. * Trigger CI * PE-9521 - Update inbound links for renamed section Point troubleshooting and known-issues links at the renamed heading "Identify the Latest Palette Agent Version". * docs: Apply batched suggestions from code review --------- * docs: Remove redundant headers from release notes * PPD-1619 - K3s removal from vClusters (#12042) * PPD-1619: K3s removal from vClusters Remove K3s as a supported Palette and Palette VerteX virtual cluster distribution across the shared vCluster and cluster-group pages. Add the K3s-blocked upgrade banner to vcluster-upgrades.md, record the removal in the 4.10.a release notes and the announcements.md Removals table, and retire the K3s-specific troubleshooting scenario in palette-dev-engine.md. Pending screenshot resolution: the distribution-selector screenshot on create-cluster-group.md still shows K3s in the dropdown and needs a re-shoot against a running 4.10.a Palette UI. * PPD-1619: drop K3s removal warnings from vCluster overview pages Warnings about a removed distribution create long-lived clutter on general overview pages. Keep the K3s-blocked upgrade warning on vcluster-upgrades.md where it applies to a real user action, and let the release notes and announcements Removals table carry the historical record. * PPD-1619: drop stale K3s distribution-selector screenshot The distribution selector no longer offers K3s, so the annotated screenshot was inaccurate. Removed the image reference from create-cluster-group.md and deleted the underlying WebP; the surrounding prose already describes the Kubernetes-only configuration. * PPD-1619: emphasize upstream K3s removal in release notes Bold the upstream-vCluster-0.33 removal clause in the announcements.md Removals row and the release-notes.md Breaking Changes bullet so the reason Palette dropped K3s stands out from the rest of the sentence. * docs: move K3s removal note to Deprecations and Removals; add upgrade note (PPD-1619) --------- * PCP-7379: Taints and system pods (#12002) * PCP-7379: Taints and system pods First draft complete. * add comments for possible changes to main section * relocate section and change focus per conversation with PM * ci: auto-formatting prettier issues * add main section. write release note * fix vale error : * EKS: add Dedicate node pool row and link * EKS: fix Dedicate row rejoin the taints table * docs: Apply batched suggestions from code review --------- * DOC-3249: microk8s known issues (#12071) * DOC-3249: microk8s known issues * Apply suggestion from @benradstone --------- * PE-9347: add Replace a Control Plane Edge Host page (#12072) * PE-9347: add Replace a Control Plane Edge Host page * docs: Apply batched suggestions from code review --------- * PE-9523: Node-level taints and labels for Edge (#12062) * PE-9523: Node-level taints and labels for Edge Document the ability to apply node-level taints and labels to individual nodes inside an Edge Native node pool. * PE-9523: Review revisions Restore the original DisableWorkerNodeCapReconcile guidance in the connected and Local UI wizard admonitions and layer the node-level taint alternative alongside it. Adds a summary of when and how to set node-level taints and labels to the Node Pools page. * PE-9523: Inline node-level field format in wizards Adds Key/Value/Effect and label format details to the node-level taints and labels step in both the connected Edge Native and Local UI cluster-creation walkthroughs. * PE-9523: Scope node-level taints to connected clusters The Local UI (Eclipse) frontend for node-level taints and labels is not yet merged, so 4.10.a ships this capability for connected Edge Native clusters only. Reverts the Local UI cluster-creation walkthrough addition and adds connected scoping to the node-pool section, installer-reference row, and release note. * PE-9523: Review revisions Adds the taint uniqueness and reserved label constraints to the merge rules list, a warning about tainting every node in a cluster, and a Tolerations for Custom Taints subsection covering CNI and CSI behavior. --------- * PCP-7533 - Resolve GKE release channel known issue and note the Regular default (#12087) * PCP-7533 - Move GKE release channel deprecation known issue to Resolved GKE deprecated the "No channel" release channel, so new GKE clusters can no longer be created without a channel. Palette defaults new GKE clusters to the Regular release channel starting with 4.10.a, so move the entry from Active to Resolved (Fix Version 4.10.a) and fold in the Regular-default and Kubernetes 1.34+ guidance. * PCP-7533 - Add GKE Limitations note for the default Regular release channel --------- * DOC-3245 - Prefill the 4.10.a highest supported Kubernetes version row (#12089) * PCP-7616: microk8s removal (#12047) * PCP-7616: microk8s deprecation * chore(ci): trigger CI again * adjusting as per Amit * DOC-3198 - Document 4.10.a breaking changes (#12095) Add Breaking Changes entries for the 4.10.a changes that the release notes did not yet cover: Splunk audit trail URL validation, the role name requirement, unique registry names on rename, the fixed Helm registry private setting, Edge Native VIP validation, the Edge Native node pool host count, and a reference entry for the K3s virtual cluster removal. Add the missing AWS subscription endpoint to the authorization entry, and correct the vCluster version from 0.34.x to 0.36.x in the release notes, the announcements Removals row, and the Upgrade Cluster Groups page. * DOC-3198 - Document 4.10.a bug fixes (#12099) Add customer-facing bug fix entries for 4.10.a under Palette Enterprise, Edge, and the VMO pack, plus one Edge improvement, and stack parent epic keys onto five existing entries. * DOC-3198 - Update deprecations and removals (#12098) * DOC-3198 - Move the Nginx deprecation row to the Disabled stage The Nginx pack is disabled in the pack registry, and the Palette 4.10.13 release notes already announce it, but the Deprecations row still described the pack as only deprecated. Reword the row to match the Disabled-stage wording used by the Kubernetes Dashboard row, and link to the pack deprecation stages. Also add the missing space before the API endpoint link in the /clusterprofiles row. Prettier re-padded the Deprecations table because the Nginx row is now its longest row. * DOC-3198 - Set the /kubeconfig removal date to November 29, 2026 Move the Target Removal Date for the deprecated /kubeconfig API endpoint from September 26, 2026 to November 29, 2026, as confirmed with the Product Manager. The removal now targets the 4.10.c release. * DOC-3198 - Move stylus.includeTui to Removals and drop its references The Palette Edge node agent stopped reading the stylus.includeTui user data flag in Palette 4.8.6 (the 4.8.0 release), when the TUI became always enabled. Move the row from Deprecations to Removals with that release and date, and point readers to stylus.disableTui for restricting TUI interaction. Remove the flag from the installer reference, from the Local UI list of fields that cannot be edited, and from the user data examples in the local management tutorial, and reword the tutorial sentence that tied the TUI to the flag. --------- * PE-9521 - Agent version release note (#12101) * PE-9521 - Agent version release note Add 4.10.a Edge Improvements entry for the Palette agent version now shown on the Edge Hosts page. * Apply suggestion from @Linus-SpectroCloud --------- * DOC-3203 - Update pack descriptions for 4.10.a (#12109) * DOC-3203 - Update pack descriptions for 4.10.a Add descriptions for the 32 active packs that the docs site rendered without one: 8 first published this cycle and 24 older packs, mostly community packs that never appear in release-notes pack tables. Remove four shadowed duplicate entries (edge-k8s, gloo, nvidia-gpu-operator, tekton-chains). The plugin's lookup is last-wins, so the earlier copies never rendered; two of them also used misspelled keys. * DOC-3203 - Clarify the two NVIDIA DRA driver pack descriptions nvidia-dra-driver and dra-driver-nvidia-gpu deploy the same upstream driver from before and after NVIDIA moved the project to the Kubernetes community. The old wording said the older pack came from "the NVIDIA repository", which now redirects to the community one. --------- * DOC-3204 - Update Known Issues for 4.10.a (#12103) * DOC-3204 - Update Known Issues for 4.10.a Move the palette-webhook rolling-upgrade downgrade and GCP control plane repave entries from Active to Resolved (Fix Versions 4.9.41 and 4.9.38). Add a GCP IaaS troubleshooting scenario so the health check workaround stays available to customers on earlier versions. * DOC-3204 - Resolve the missing multipath-tools known issue Move the missing multipath-tools entry from Active to Resolved (Fix Version 4.10.13), and add an Edge troubleshooting scenario so the Dockerfile workaround stays available to customers on earlier CanvOS versions. --------- * docs: replace the 4.10.a Packs scaffold with the fold-in placeholder (#12150) The 4.10.a release section was scaffolded before the release-run fold-in landed, so it still carried the old markerless Packs block and no placeholder. The release-week Component Updates run (base branch docs-rel-4-10-a) exits when the placeholder is missing. Swap the empty Packs, Pack Notes, and Deprecations and Removals headings for the placeholder, wrapped in an HTML comment so the branch still builds. * PCP-7616: drop MicroK8s from the infrastructure profile Kubernetes row (#12154) * DOC-3290: document opt-in Zot certificate rotation for the management appliances * DOC-3290: apply review fixes (version tag, split steps, product names) * DOC-3288 - Add iam:ListRoles to the Controllers EKS Policy (#12171) * DOC-3288 - Add iam:ListRoles to the Controllers EKS Policy Palette deletes the IRSA roles it manages for an EKS cluster by listing roles with iam:ListRoles and filtering on the ownership tag. The documented PaletteControllersEKSPolicy did not grant it, so cluster deletion left the roles behind. Add the action in its own statement, because iam:ListRoles does not support resource-level permissions and needs Resource "*". Remove the iam:ListRoles rows from the EKS pack coverage tables, which the policy now covers, and add a 4.10.a Docs and Education release note. * DOC-3288 - Add an Upgrade Notes entry for iam:ListRoles Move the action for existing EKS clusters into the 4.10.a Palette Enterprise Upgrade Notes so it is not missed, and trim the Docs and Education entry to the documentation change with a link to it. * DOC-3288 - Set Last Update to the October 9 release date --------- * DOC-3198 - Add 4.10.a bug fixes and move release date to October 9 (#12174) Rerun of the 4.10.a customer-found bug fix filter adds PCP 7662 and PCP 7737 under Palette Enterprise and PE 9703 under Edge. The 4.10.a release date moves from October 4 to October 9, 2026 in the release notes heading, the Removals table, and the Resolved Known Issues table. * PE-9527: add Hadron Tech Preview release note and admonition (#12172) * PE-9527: add Hadron Tech Preview release note and admonition * Apply suggestion from @benradstone * ci: auto-formatting prettier issues --------- * PVM-1183: pull VLAN filtering docs from 4.10.a (#12177) VLAN filtering moved to the next VM Launchpad drop (PVM-1304), so the content from #12035 must not publish with 4.10.a. * docs: order version-specific upgrade notes newest first (#12178) * docs: order version-specific upgrade notes newest first List the version-specific Upgrade Notes on the Palette and VerteX management appliance, Kubernetes, and VMware upgrade guides in reverse chronological order of target version, so the notes for the latest releases appear at the top. * docs: fix the empty product name in the appliance 4.7.x upgrade notes The upgrade-palette-upgrade-notes partial used {props.version}, which neither appliance page passes, so both 4.7.27 and 4.7.15 notes rendered "before upgrading ." Use {props.edition}, which both pages already pass. --------- * DOC-3290: name the toggle, scope the default-off note to upgrades * DOC-3290: name the Enable Certificate Rotation toggle, scope it to upgrades and the internal registry * DOC-3290: apply Shashank's review and confirm that Update applies the toggle directly Make the Zot release note the first 4.10.a Upgrade Notes bullet with a User action required lead-in, and note manual rotation as the alternative in both the release note and the appliance Upgrade Notes partial. Gaurav confirmed that Update applies the change directly; Review Changes appears only for upgrades from uploaded content. * DOC-3290: add the Container Registry path and CA script step, and match step 37 to the new installer * DOC-3290: add the registry CA update script steps * DOC-3290: apply review fixes and drop the script TODO * DOC-3290: note that the registry CA script runs only once --------- (cherry picked from commit 24921c8) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Linus Bourque <linus@spectrocloud.com> Co-authored-by: Ben Radstone <benjamin.radstone@spectrocloud.com> Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: brent-eritou <brent.eritou@spectrocloud.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Santhosh <santoshdaivajna@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: vault-token-factory-spectrocloud[bot] <133815545+vault-token-factory-spectrocloud[bot]@users.noreply.github.com> Co-authored-by: Kurt Dawn <kurt.dawn@spectrocloud.com>
spectro-gh-kdawn
added a commit
that referenced
this pull request
Oct 17, 2026
Port DOC-3290 (#12173) Profile Config section tables into the split create-cluster partial. Move DRBD module loading reference to the Piraeus CSI integration page, keeping only the DRBD Compile Mode row in the install guide. Co-Authored-By: Claude Opus 5.5 <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.
✅ Pull Request Checklist
Before submitting your PR for review, please complete this checklist to ensure quality.
Checklist
auto-backportlabel, as well as thebackport-version-**labels.backport-version-4-10([version-4-10] DOC-3290: document opt-in Zot certificate rotation for the management appliances (#12173) #12236).notify-slacklabel once this checklist has been completed. The team will be notified and review your PR.Good job! 👏👏👏
📝 Describe the Change
Documents the opt-in Zot certificate rotation for the Palette and VerteX management appliances, which shipped as 4.10.25 on October 14.
_partials/self-hosted/upgrade/_zot-certificate-rotation.mdx, first Upgrade Notes bullet on both appliance upgrade pages): rotation is off after an upgrade. To turn it on, resume paused agent upgrades, turn on Applications Config > Container Registry > Enable Certificate Rotation, select Update, and then run the one-time registry CA update script (update_registry_ca.py). Tenant clusters get the rotated certificate automatically._partials/self-hosted/management-appliance/_installation-steps-enablement.mdx, step 37): the installer now groups its options into five sections (Networking, Operating System, Storage, Container Registry, Management Plane), so the two old tables are now five, with new Enable Certificate Rotation, DRBD Compile Mode, and Enable OpenTelemetry rows. The DRBD subsection now points to DRBD Compile Mode in place of editing thepiraeus-operatorpack YAML.Follow-up: the 4.10.a release-note bullet, the
4.10.25install-page Kubernetes rows, and the PLT-2463 removal from Week 41 are in #12237. Once 4.10.26 ships, the script steps apply to 4.10.25 only, because PEM-12279 automates them; that qualifier lands with the 4.10.26 release notes (#12223).💻 Changed Pages
🎫 Jira Tickets