docs(enterprise): remove pre-flight check pages from version-26.1 - #1704
Open
MichaelTansiniSeqera wants to merge 13 commits into
Open
docs(enterprise): remove pre-flight check pages from version-26.1#1704MichaelTansiniSeqera wants to merge 13 commits into
MichaelTansiniSeqera wants to merge 13 commits into
Conversation
Signed-off-by: MichaelTansiniSeqera <michael.tansini@seqera.io>
…roubleshooting page - Tighten prose in preflight-checks.md (main + version-26.1): active-verb Task headings, remove hedges and padding, split loose connectors, drop decorative em-dashes - Move Error reference section to new troubleshooting_and_faqs/preflight_checks_troubleshooting.md with a pointer link on the source page, per the docs-structure troubleshooting convention - Add the new troubleshooting page to the enterprise + version-26.1 sidebars - Add `last updated` frontmatter to match the compute-envs sibling convention Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
- Remove work directory section from pre-flight checklist — no longer validated - Clarify that launch-time CE status and credential status checks read from the database, not live cloud probes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pre-flight checks (COMP-1724) shipped in 26.2. They were not included in the ENTERPRISE-26.1.x branch and are not present in the v26.1.4 release tag. Remove the two pages and their sidebar entries from the frozen 26.1 versioned docs to prevent customers on 26.1 from following instructions for a feature that is not available in their version. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
MichaelTansiniSeqera
requested review from
christopher-hakkaart and
justinegeffen
August 3, 2026 11:18
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
2 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.
Summary
Pre-flight checks (COMP-1724) shipped in 26.2. The feature is not present in the
ENTERPRISE-26.1.xbranch and is not reachable from thev26.1.4-enterprisetag.Two pages were added to the frozen 26.1 versioned docs on 2026-07-24, after the 26.1.4 cut. Customers on 26.1 would see instructions for a feature that does not exist in their install.
Changes:
platform-enterprise_versioned_docs/version-26.1/compute-envs/preflight-checks.mdplatform-enterprise_versioned_docs/version-26.1/troubleshooting_and_faqs/preflight_checks_troubleshooting.mdplatform-enterprise_versioned_sidebars/version-26.1-sidebars.jsonThe pages and their sidebar entries remain untouched in
platform-enterprise_docs/(current/latest, which is 26.2+) and in theplatform-enterprise_docs/sidebar.Test plan
platform-enterprise_docs/) pre-flight pages are unaffected🤖 Generated with Claude Code