Update from code changes: document lastUpdatedDate frontmatter - #6974
Open
mintlify[bot] wants to merge 2 commits into
Open
Update from code changes: document lastUpdatedDate frontmatter#6974mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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.
Summary
The "Last modified on" footer now uses the
lastUpdatedDatefrontmatter field before falling back to the Git commit date or deployment timestamp. This is useful when Git history doesn't reflect real content updates, such as for docs mirrored from another system. The precedence is nowlastUpdatedDatefrontmatter → last Git commit date → most recent deployment timestamp. Documented on the Pages guide and referenced from the settings reference. Triggered by https://github.com/mintlify/mint/pull/10133.Changes
organize/pages.mdx: AddedlastUpdatedDatefrontmatter field, example, and precedence to the "Last modified timestamp" section.organize/settings-reference.mdx: Noted the per-pagelastUpdatedDateoverride next tometadata.timestamp.es/,fr/, andzh/translations oforganize/pages.mdx.Note
Low Risk
Documentation-only updates across English and translated pages; no runtime or config schema changes in this repo.
Overview
Documents the
lastUpdatedDatepage frontmatter field so authors can override the “Last modified” footer date when Git history or deployment time is wrong (for example mirrored docs).The Pages guide (
organize/pages.mdxandes/fr/zhtranslations) adds usage (date-only or ISO 8601), a YAML example, and precedence:lastUpdatedDate→ last Git commit → latest deployment; invalid or empty values fall back to the commit date. Existing per-pagetimestampshow/hide behavior is unchanged.The settings reference (
metadata.timestamp) now points readers to that section for the per-page date override.Reviewed by Cursor Bugbot for commit 233220b. Bugbot is set up for automated code reviews on this repo. Configure here.