-
Couldn't load subscription status.
- Fork 476
Archive cross-version documentation for v22.2 and earlier #20799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Complete 3-step cross-version archival process removing support for v22.2, v22.1, v21.2, v21.1, v20.2, and v2.1 documentation versions. **Major Changes:** - Delete 1,769 archived version image assets - Fix 40+ cross-version references to point to supported versions - Update backward-incompatible links to use v23.2 (earliest supported) - Fix Jekyll SSL certificate verification for Ruby 3.4.3 + macOS - Add required Ruby 3.x gem dependencies **Cross-Version Link Fixes:** - Fix backward-incompatible files (9 files): v22.2 Jekyll links → v23.2 relative paths - Fix show-ranges deprecation notices: v22.2 links → archived documentation - Fix release notes and Kubernetes upgrade references - Fix replication zone mapping references across all supported versions **Infrastructure:** - Preserve existing minimal infrastructure (releases/v*.md stub pages) - Add openssl_fix.rb for Jekyll SSL bypass - Update Gemfile with Ruby 3.x compatibility gems - Fix Liquid syntax errors in image paths **Verification:** - All corrected links verified to exist and function - Cross-version references now cleanly separated (v23.1+ supported) - Jekyll server compatibility restored
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
❌ Deploy Preview for cockroachdb-docs failed. Why did it fail? →
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't review this in more detail until the build is working. I spotted a couple of obvious issues that I left comments about.
Please consider breaking this into several smaller PRs. It's going to be difficult for me to meaningfully review a PR with this many changed files in it and trust that what we're merging won't have unintended consequences even if the build tests do pass.
| gem "rss" | ||
| gem "webrick" | ||
| gem "jekyll-minifier" | ||
| gem 'csv' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please let's not do rubygems tweaks in this docs PR
| @@ -0,0 +1,294 @@ | |||
| # Cross-Version Links Analysis Report | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please don't add LLM-generated plan files to the docs repo
| @@ -0,0 +1,41 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think this is a good home for this script, it looks like a one-off LLM script
| @@ -0,0 +1,14 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think this is a good home for this script, this looks like a one-off LLM fixup script
Summary
Complete 3-step cross-version archival process removing support for v22.2, v22.1, v21.2, v21.1, v20.2, and v2.1 documentation versions. This
follows the established pattern of archiving unsupported versions while preserving access through minimal infrastructure.
Changes Made
🗂️ Asset Cleanup
images/v2.1/,images/v20.2/,images/v21.1/,images/v21.2/,images/v22.1/,images/v22.2/🔗 Cross-Version Link Fixes
🛠️ Infrastructure Improvements
openssl_fix.rb)csv,logger,base64,bigdecimal,mutex_m)📋 Link Verification
Archival Strategy
This implementation follows the established 3-step archival process:
releases/v*.md) that redirect to archived documentationFiles Changed