morningman opened a new pull request, #4211: URL: https://github.com/apache/doris-website/pull/4211
## Problem and resulting behavior The Japanese locale is implemented and validated but production builds still omit it. This publishes the existing Japanese pages now: pages without a valid Japanese translation retain the same-version English document and display the Japanese translation-status notice plus a link to the English source. The four currently valid translated documents remain available; 3,282 required Dev/4.x/community documents are still pending translation. Translation coverage is reported separately from reachable fallback routes. Both production deploy workflows now enable `DORIS_ENABLE_JA=true` and validate the built Japanese pages before either OSS upload or `asf-site` publication. The validation checks the page language, translation notice/state, canonical and noindex rules, sitemap and Japanese search exclusion for fallback pages. The job-level flag can be set to `false` in both workflows for rollback; the Japanese-only verification step then skips. The cron workflow previously inspected a nonexistent manual `branch` input. On push/schedule that could skip its master deployment and enter the branch deployment step. It now always publishes the master site. The manual workflow checks out its requested branch, and both workflows pass the deployed commit SHA to the publish action. Manual and cron deployments share a concurrency group. Deployment workflow changes are classified as shared build inputs; the Japanese full-build and document-scope CI jobs run on this PR. ## Validation - 38 i18n/build unit tests passed; workflow YAML parsed; `git diff --check` passed. - Full Node 20 en/zh-CN/ja build of all active versions and static verification are in progress locally. - The PR is draft until the full-memory, document, browser, search and baseline checks pass. No deployment occurs from the PR checks. ## Rollback Set `DORIS_ENABLE_JA` to `false` in both production jobs, rebuild and publish the en/zh-CN artifact to `asf-site`; its `force_orphan` publication removes `/ja/` from the main site. OSS uses `onlyUpload`, so old `/ja/` objects in the asset bucket require targeted deletion and CDN invalidation if direct asset URLs must also be disabled. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
