docs: Fix 404 helm-charts links on Platform Helm page [EDU-1330] - #1706
Merged
Conversation
All four helm-charts links on the Platform Enterprise Helm installation page 404, across all five doc versions that carry it (next, 26.1, 25.3, 25.2, 25.1) — 20 links in total. Two independent upstream changes in seqeralabs/helm-charts compounded: 1. Bare-numeric tags were renamed to <chart>-<version>. Only 0.16.1 is still un-prefixed, so /tree/0.36.1/... can never resolve, and GitHub does not redirect a missing ref. 2. The platform chart moved from platform/ to charts/platform/ when the repo became a multi-chart monorepo, between 0.20.1 and 0.30.0. This is why even the next docs — which did carry the platform- prefix — still 404. PR #1660 substituted 0.20.1 -> 0.36.1 in the URLs and changed nothing else, inheriting both the missing prefix and the pre-monorepo path. Adds the tag prefix and the charts/ segment. The studios and pipeline-optimization links are deliberately untouched: those charts kept the platform/charts/<name> layout and already resolve. Reported by a customer via FD-7794. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Rob Syme <rob.syme@gmail.com>
robsyme
requested review from
a team,
christopher-hakkaart and
justinegeffen
as code owners
August 3, 2026 17:04
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
justinegeffen
approved these changes
Aug 3, 2026
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.
Fixes EDU-1330. Reported by a customer via FD-7794.
Problem
All four
seqeralabs/helm-chartslinks on the Platform Enterprise Helm installation page 404, in every doc version that carries the page (next, 26.1, 25.3, 25.2, 25.1) — 20 dead links. They've been broken since 2026-07-20.Two independent upstream changes compounded:
<chart>-<version>. Of 242 tags, only0.16.1is still un-prefixed, so/tree/0.36.1/...can never resolve — and GitHub doesn't redirect a missing ref, so it fails hard.platform/tocharts/platform/betweenplatform-0.20.1andplatform-0.30.0. This is why even thenextdocs, which did carry theplatform-prefix, still 404.#1660 substituted
0.20.1→0.36.1in the URLs and changed nothing else, inheriting both the missing prefix and the pre-monorepo path. It also preserved a pre-existing inconsistency — thenextcopy usedplatform-0.20.1while the versioned copies used bare0.20.1— so after the bump the two sets fail for different reasons.Change
Adds the tag prefix and the
charts/path segment:The studios and pipeline-optimization links are deliberately untouched — those charts kept the
platform/charts/<name>layout and already resolve, so a repo-wide sweep would have broken them.Verification
Status-checked every unique helm-charts URL in the repo before and after. 6 of 15 were 404; all 12 distinct URLs now return 200.
The one remaining 301 is GitHub redirecting
tree→blobforexamples/seqera-ai, which is a file. Pre-existing and harmless.Why CI didn't catch this
Worth flagging separately, because it's the more interesting finding.
links.ymlruns lychee over the docs, but its last output was #440 on 2025-02-08 and all 218 runs in the retained history failed. Three independent defects:pull_requesttrigger. Triggers areschedule(Sunday 18:00),workflow_dispatch,repository_dispatch. Even a working checker could not have blocked docs: Update platform helm chart to latest #1660 — at best it would have complained the following Sunday. Onlycheck-internal-links.ymlgates PRs, and that covers internal links only.--base .has been there since the workflow was written in July 2024, but lychee 2.x requires an absolute path or URL and moved root-relative local resolution to--root-dir. The binary exits 2 after ~200ms without checking a link. Because that's an arg-parse error rather than a link failure,steps.lychee.outputs.exit_codeis never set, socreate-issue-from-fileis skipped too — no report issue, no signal at all.'./**/*.mdx'; the enterprise docs are 1284.mdagainst 75.mdx.platform-helm.mdwas never in scope.Fixing all three (add
pull_request, swap--base .for--root-dir "$GITHUB_WORKSPACE", glob'./**/*.md*') is what would actually catch the next one. Not done here — it's a separate change, and the first successful run will surface 18 months of accumulated rot, so it'll likely need an allowlist or a soft-fail period before it can gate PRs.Also not addressed
Editorial, tracked on EDU-1330:
v26.1.3), which postdates those releases.v26.1.4) exist.🤖 Generated with Claude Code