[fix] revert per-locale split build and drop legacy dev docs#3616
Merged
Conversation
Restore the single bilingual `docusaurus build --locale en --locale zh-CN` invocation in the cron and manual deploy workflows; the prior per-locale split produced different webpack content hashes for EN and ZH, leaving zh-CN HTML referencing /assets/styles.<zh-hash>.css that only existed under build/zh-CN/ and 404'd under root. Disable building the unversioned (dev) tree of the legacy docs plugin — the dev version now lives under the docs-next plugin only — by removing "current" from versions.json and setting includeCurrentVersion: false on the classic preset's docs config. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previous DOCS_VERSIONS=current env still tried to filter the legacy docs plugin to its (now-removed) current version, producing "Docs option lastVersion: current is invalid. Available version names are: 4.x, 3.x, 2.1". Skipping the legacy plugin via SKIP_DOCS=true leaves docs-next as the only plugin building the unversioned content. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Same lastVersion-invalid error as docs-next-build.yml: build-check fed DOCS_VERSIONS=current to the legacy docs plugin (sidebars.ts and no-versioned-change fallback paths), but the legacy plugin no longer ships current. Map all four call sites to 4.x so the smoke build hits a real version. Also note in comments that docs/ and i18n current dirs are no longer compiled (PR apache#3610 forbids edits there). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
SKIP_DOCS=true removed the default content-docs plugin entirely, which broke SSG of /archive-docs and /community/how-to-contribute/docs-format- specification — both use a navbar with type: docsVersionDropdown that defaults to pluginId='default'. Instead, build the legacy plugin with DOCS_VERSIONS=4.x so the plugin instance and its global data exist.
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.
Restore the single bilingual
docusaurus build --locale en --locale zh-CNinvocation in the cron and manual deploy workflows; the prior per-locale split produced different webpack content hashes for EN and ZH, leaving zh-CN HTML referencing /assets/styles..css that only existed under build/zh-CN/ and 404'd under root.Disable building the unversioned (dev) tree of the legacy docs plugin — the dev version now lives under the docs-next plugin only — by removing "current" from versions.json and setting includeCurrentVersion: false on the classic preset's docs config.