kevinjqliu opened a new pull request, #179: URL: https://github.com/apache/datafusion-site/pull/179
Relates to #178 ## What changes are included in this PR? Adds `output: 'blog'` to `publish-site.yml`, matching `stage-site.yml`. The publish workflow was missing this parameter, so the pelican action defaulted to `output: 'output'`. This caused a mismatch with `.asf.yaml` (`subdir: blog`), which was worked around with `.htaccess` rewrite rules. Those rules have a regex bug that exposes the internal `/output/` path for any blog post with a version number in its slug: - `/blog/2026/04/18/datafusion-comet-0.15.0` → 301 → `/blog/output/...` ❌ - `/blog/2026/04/02/datafusion-53.0.0` → 301 → `/blog/output/...` ❌ With this fix, content lands in `blog/` on `asf-site`, matching what `.asf.yaml` expects. The `.htaccess` rewrite-to-output hack becomes unnecessary. ## Follow-up After this deploys, a separate PR to `asf-site` should remove the stale `output/` directory and simplify `.htaccess` to only the CSP directive. -- 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]
