Repository navigation
docs: stop rewriting links to /stable/ to the built version - #1157
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: QUIET Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe documentation URL replacement pattern now matches only paths with a Priority: ⬇️ Low Change: Bug fix Merge Risk: ⚪ Minimal · up to Only versioned Scylla documentation links are rewritten; stable and unversioned links remain unchanged. No actionable merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
724272b to
0cb70c2
Compare
The replacements hook pins every java-driver.docs.scylladb.com/<x>/ link to the version being built. On 3.x pages that turns the deprecation notice's link to the 4.x docs at /stable/ into a link back to 3.x. Rewrite only scylla-* version slugs; /stable/ and unversioned links are deliberate and stay as written. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
0cb70c2 to
d78482d
Compare
Depends on: nothing
Merge before: the fast-forward of
scylla-4.19.2.x(4.x order: #1157 → fast-forward → #1158)Needed by: the fast-forward of
scylla-3.11.5.xtoscylla-3.x, which also needs the 4.19.2.x fast-forward so that/stable/upgrade_guide/from_3x/existsThe
replacementshook inconf.pyrewrites everyjava-driver.docs.scylladb.com/<x>/link in page content to the version being built. On the live/scylla-3.11.5.x/landing page, the deprecation notice's "documentation" link (#919), written as/stable/, renders as/scylla-3.11.5.x/: it sends 3.x readers back to 3.x.scylla-3.xhas two more such links (#1001), which would render as/scylla-3.11.5.x/upgrade_guide/from_3x/after the fast-forward, a 404.scylla-*version-slug segments, the only kind the content uses besidesstable/stable/, the bare root and unversioned paths as written, so the README's/stable/api/link stays putVerified: ran the current
scylla-4.xrule and this one over every.md/.rstfile ofscylla-4.x,scylla-4.19.2.x,scylla-4.19.0.x,scylla-4.18.1.x,scylla-3.11.5.xandscylla-3.x, each with its own slug. Only/stable/lines change: 1 on 3.11.5.x, 3 on 3.x, the README[API docs]line on 4.x; 0 on the published 4.x versions. Edge cases (/stable),/stable#,/stable-3/,/manual/core/,[url](url/), the bare root, an old versioned link) behave as intended.cd docs && make test: exit 0, no warnings. Not covered: the multiversion publish, and the live site before the two fast-forwards.Refs: #1001
Jira: DRIVER-854
🤖 Generated with Claude Code