Closed
Conversation
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
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.
🔍 Description #107
This PR fixes a critical bug where the sitemap.xml file was not being correctly generated or updated during deployment.
The Issue:
The Google Search Console was unable to read the sitemap because the deployed version was stale or missing new routes.
Investigation revealed that the GitHub Actions workflow (release.yml) was running
npx next builddirectly. However, our package.json defines thebuildscript as"npm run generate:sitemap && next build". By bypassing the package script, the CI pipeline was skipping the sitemap generation step entirely.The Fix:
Updated .github/workflows/release.yml to use
npm run buildinstead ofnpx next build. This ensures thatgenerate:sitemapruns automatically before the Next.js build, guaranteeing that every deployment has a fresh, valid sitemap.