Fix #2598, shift to last_modified_at instead of last_updated. #3493
+3
−2
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
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
❌ Deploy Preview for relaxed-lollipop-b6bc17 failed. Why did it fail? →
|
george-gca
approved these changes
Jan 31, 2026
Collaborator
|
Thanks for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Use
last_modified_atrather thanlast_updated. So that the jekyll-sitemap plugin automatically looks for the standardlast_modified_atfront matter field to generate the<lastmod>tag in yoursitemap.xml.It fixes #2598
Also, it preserves backward compatibility, as the updated metadata logic prioritizes the
page.last_modified_at, and defaults topage.last_updated.