Skip to content

docs: cut 6.1.0 versions for user_docs, admin_docs, developer_docs, components#40126

Merged
rusackas merged 1 commit into
masterfrom
chore/docs-cut-6.1.0
May 18, 2026
Merged

docs: cut 6.1.0 versions for user_docs, admin_docs, developer_docs, components#40126
rusackas merged 1 commit into
masterfrom
chore/docs-cut-6.1.0

Conversation

@rusackas
Copy link
Copy Markdown
Member

@rusackas rusackas commented May 14, 2026

SUMMARY

Cuts a 6.1.0 snapshot for all four versioned Docusaurus sections (user_docs, admin_docs, developer_docs, components).

Cut from a clean master after the prerequisite work landed:

With #40171 in place, the snapshot lands at user_docs_versioned_docs/version-6.1.0/ alongside the other three sections instead of the bare versioned_docs/version-6.1.0/ outlier — addresses the consistency concern raised on the previous version of this PR.

Versioning behavior: lastVersion stays at current for every section, so the canonical URLs (/user-docs/..., /admin-docs/..., /developer-docs/..., /components/...) continue to render content from master. The current version is consistently labeled "Next" with an unreleased banner across all four sections, and 6.1.0 is a historical pin accessible only via its explicit version segment.

Component playground: previously disabled: true in versions-config.json, now enabled and versioned. The plugin block in docusaurus.config.ts was already gated only by the disabled flag, so no other code changes were needed to bring it back online.

What's in the snapshot:

  • All MDX content for the four sections at the SHA we cut from.
  • Auto-generated content captured fresh: 74 database pages (from superset/db_engine_specs/ metadata), ~1,800 API reference files (from static/resources/openapi.json via gen-api-docs), 59 component pages (from Storybook stories).
  • Data imports frozen at cut time into snapshot-local _versioned_data/ dirs:
    • user_docs_versioned_docs/version-6.1.0/_versioned_data/src/data/databases.json — canonical 80-database diagnostics from master (preserved by the generator's input-hash cache, not regenerated to a local-Flask-env fallback).
    • admin_docs_versioned_docs/version-6.1.0/_versioned_data/data/countries.json — supported-countries list for the Country Map Tools page.
    • admin_docs_versioned_docs/version-6.1.0/_versioned_data/static/feature-flags.json — feature flag tables.
    • developer_docs_versioned_docs/version-6.1.0/_versioned_data/static/data/components.json — component playground index metadata.
  • Import paths in deeply-nested files rewritten (../../../src/... etc.) so they still resolve correctly from one directory deeper inside the snapshot.
  • developer_docs/extensions/overview.md snapshot has the FIXED ./mcp.md form (from fix(docs): tighten onBrokenLinks to throw and fix surfaced broken links #40102), so the SPA-nav 404 isn't baked into the 6.1.0 version.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A (versioning change; surfaces existing content under new URL paths).

TESTING INSTRUCTIONS

cd docs
yarn install
yarn build
yarn serve

Verify:

  1. The version dropdown badge appears on all four sections (/user-docs/..., /admin-docs/..., /developer-docs/..., /components/...) and includes both Next and 6.1.0.
  2. The canonical URL for each section (without a version segment) renders the current content with the "unreleased" banner, matching the latest source.
  3. Adding /6.1.0 to any section URL renders the historical snapshot with no banner.
  4. country-map-tools.mdx (admin_docs/6.1.0) renders all 201 countries from a frozen JSON.
  5. feature-flags.mdx (admin_docs/6.1.0) renders the feature-flag tables from a frozen JSON.
  6. databases/index.mdx (user_docs/6.1.0) renders the 80-database list from a frozen databases.json.
  7. From /developer-docs/extensions/overview/ (with trailing slash), the "Next Steps" bullets click through correctly to /developer-docs/extensions/X (not /developer-docs/extensions/overview/X).

yarn build already validated locally — passes with onBrokenLinks: throw. Only warnings are pre-existing anchor warnings on /community#superset-community-calendar (unrelated; tracked separately).

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@bito-code-review
Copy link
Copy Markdown
Contributor

bito-code-review Bot commented May 14, 2026

Bito Automatic Review Skipped - Large PR

Bito didn't auto-review this change because the pull request exceeded the line limit. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.

@dosubot dosubot Bot added the doc Namespace | Anything related to documentation label May 14, 2026
@netlify
Copy link
Copy Markdown

netlify Bot commented May 14, 2026

Deploy Preview for superset-docs-preview ready!

Name Link
🔨 Latest commit 4ee42fe
🔍 Latest deploy log https://app.netlify.com/projects/superset-docs-preview/deploys/6a080274469fe300081d085a
😎 Deploy Preview https://deploy-preview-40126--superset-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.16%. Comparing base (8d2b655) to head (4ee42fe).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #40126   +/-   ##
=======================================
  Coverage   64.15%   64.16%           
=======================================
  Files        2591     2591           
  Lines      138162   138162           
  Branches    32048    32048           
=======================================
+ Hits        88642    88649    +7     
+ Misses      47991    47984    -7     
  Partials     1529     1529           
Flag Coverage Δ
hive 39.45% <ø> (ø)
javascript 67.01% <ø> (+<0.01%) ⬆️
mysql 59.15% <ø> (ø)
postgres 59.23% <ø> (ø)
presto 41.14% <ø> (ø)
python 60.67% <ø> (ø)
sqlite 58.87% <ø> (ø)
unit 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@michael-s-molina
Copy link
Copy Markdown
Member

@rusackas Isn't possible to have a 6.1.0 folder with the remaining structures underneath instead of multiple folders with a 6.1 suffix?

@rusackas
Copy link
Copy Markdown
Member Author

rusackas commented May 15, 2026

@rusackas Isn't possible to have a 6.1.0 folder with the remaining structures underneath instead of multiple folders with a 6.1 suffix?

Well... I can tidy it up, I think. The three sections (user/admin/dev) are versioned independently, since that's what we decided to do, and the versioning might get MORE hairy if we start considering package/extension/sdk versioning.

That said, I see two fixes I wanna make:

  • versioned_docs is vestigial, and should be user_docs now
  • Docusaurus makes a folder for the sidebar and for the content... I'll see if I can get that in one directory. Then at least there'd be one folder per versioned area of the site.

@rusackas
Copy link
Copy Markdown
Member Author

@michael-s-molina it SEEMS that the two-folder thing (sidebars and content) is hard-coded into Docusaurus, so we can't combine those unless we wanna fork Docusaurus (no thanks!)

That said, I'll update versioned_docs to user_docs on a new PR, then adjust this one when it merges.

Of course, we CAN revisit the convo of NOT versioning the sections of the site independently at all... we were steering toward flexibility, but that also means complexity.

@sfirke
Copy link
Copy Markdown
Member

sfirke commented May 15, 2026

I approved #40171 - are you going to merge that into here, or close this in favor of a new PR that includes that one?

…omponents

Snapshots all four versioned Docusaurus sections at v6.1.0, cut from
master after the version-cutting tooling (#39837), broken-internal-
links fix (#40102), and user_docs rename (#40171) all landed. With
the rename in place, all four sections now produce parallel-named
files at the docs/ root (no more bare `versioned_docs/` outlier).

Versioning behavior: lastVersion stays at current for every section,
so the canonical URLs (/user-docs/..., /admin-docs/...,
/developer-docs/..., /components/...) continue to render content
from master. The current version is consistently labeled "Next"
with an unreleased banner, and 6.1.0 is a historical pin accessible
only via its explicit version segment.

Component playground: previously disabled: true in versions-config.json,
now enabled and versioned.

Snapshot includes:
- All MDX content for the four sections.
- Auto-gen captured fresh: 74 database pages (engine spec metadata),
  ~1,800 API reference files (openapi.json), 59 component pages
  (Storybook stories).
- Data imports frozen at cut time into snapshot-local _versioned_data/
  dirs:
    user_docs_versioned_docs/version-6.1.0/_versioned_data/src/data/databases.json
      (canonical 80-database diagnostics from master, preserved by the
      generator's input-hash cache)
    admin_docs_versioned_docs/version-6.1.0/_versioned_data/data/countries.json
    admin_docs_versioned_docs/version-6.1.0/_versioned_data/static/feature-flags.json
    developer_docs_versioned_docs/version-6.1.0/_versioned_data/static/data/components.json
- Import paths in deeply-nested files rewritten so they still resolve
  from one directory deeper inside the snapshot.
- developer_docs/extensions/overview.md snapshot has the FIXED
  ./mcp.md form (from #40102), so the SPA-nav 404 isn't baked into
  the 6.1.0 version.

Verified via full yarn build: exit 0, no broken links surfaced by
onBrokenLinks: throw.
@rusackas rusackas force-pushed the chore/docs-cut-6.1.0 branch from 4266d36 to 4ee42fe Compare May 16, 2026 05:36
@rusackas rusackas changed the title docs: cut 6.1.0 versions for docs, admin_docs, developer_docs, components docs: cut 6.1.0 versions for user_docs, admin_docs, developer_docs, components May 16, 2026
@rusackas
Copy link
Copy Markdown
Member Author

@sfirke that one just changed the build stuff... now that it's merged (thanks!) this has the docs cut re-built with the new directory naming.

@rusackas
Copy link
Copy Markdown
Member Author

@sfirke @villebro @sadpandajoe this cut should finally be good to go, so we can call it done!

Copy link
Copy Markdown
Member

@sadpandajoe sadpandajoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rusackas rusackas merged commit 6fa0b48 into master May 18, 2026
79 checks passed
@rusackas rusackas deleted the chore/docs-cut-6.1.0 branch May 18, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Namespace | Anything related to documentation preset-io

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants