fix(ci): sitemap generation #165
Merged
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.
Fix: Sitemap Not Updating in CI/CD
🐛 The Problem
The user reported that
sitemap.xmlwas buggy or not being read correctly by Google Search Console.Upon investigation, it was found that the deployed
sitemap.xmlmight be stale or not reflecting the latest routes because the generation script was not running during the automated deployment.🔍 Root Cause Analysis
In
package.json, the build script is defined as:This script ensures that the sitemap is regenerated before the Next.js build occurs.
However, the GitHub Actions workflow (
.github/workflows/release.yml) was explicitly running:By running
next builddirectly vianpx, the CI pipeline was bypassing thenpm run generate:sitemapstep defined inpackage.json. Consequently, the sitemap in theout/directory was either missing, stale, or relying on a previously committed version.🛠 The Solution
I have updated the
.github/workflows/release.ymlfile to use the project's defined build script instead of the default Next.js command.Change:
✅ Verification Steps
To verify this fix:
✅ Sitemap generated...in the logs before the Next.js build starts.https://physicshub.github.io/sitemap.xmlto ensure it matches the latest content.