dengliming opened a new issue, #1136: URL: https://github.com/apache/shenyu-website/issues/1136
## Blog posts have no `date`, and CI uses a shallow clone 21 of 22 `blog/*.md` files (and all 21 zh counterparts under `i18n/zh/docusaurus-plugin-content-blog/`) have no `date` frontmatter and no date in the file name. Only `SPI-SourceCode-Analysis-SPI.md` has `date: 2022-09-12`. Docusaurus then falls back to the git file-creation time. `.github/workflows/deploy.yml` uses `actions/checkout@v2` without `fetch-depth: 0` (depth 1), so on the deployed site every post gets the HEAD commit date and the blog order is arbitrary. **Fix:** add `date:` to every blog post (and set `fetch-depth: 0` in the workflow as a safety net). ## Wrong dates / titles in news frontmatter (en + zh copies) | File | Problem | |---|---| | `news/Apache-ShenYu-Committer-2022-02-28.md` | `date: 2021-02-28` (before ShenYu entered the incubator) → should be `2022-02-28` | | `news/Apache-ShenYu-Committer-2026-01-21.md` | `date: 2025-01-21` while file name and slug say 2026 | | `news/Apache-ShenYu-release-version-2.5.1.md` | `date: 2022-02-04`, which sorts it before 2.4.3 (2022-04-18); most likely 2023 | | `news/Apache-ShenYu-release-version-2.7.0.3.md` | en `title` / `description` say **"2.7.3"**, should be "2.7.0.3" (zh is correct) | ## zh OSPP2025 translation is never published - en: `news/Apache-ShenYu-OSPP2025-Summary-2026-01-07.md` - zh: `i18n/zh/docusaurus-plugin-content-blog-news/Apache-ShenYu-OSPP2025-Summary1-2026-01-07.md` (note the extra `1`) Docusaurus matches translations by relative path, so the zh file is ignored and `/zh/news/...` shows the English post. Rename the zh file to match. ## Minor - 9 news posts have no author at all: release posts 2.4.3, 2.5.1, 2.6.0, 2.7.0, 2.7.0.1, 2.7.0.2, 2.7.0.3, 2.7.1 and WASM 1.0.0. - zh news files `Committer-2022-08-08`, `Committer-2026-01-06` and `GSOC2023` still have English titles. - None of the 104 posts has a `<!-- truncate -->` marker, so `/blog` and `/news` list pages render every post in full. -- 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]
