chore(docs): sync development -> documentation (3.7.0, conflict resolved)#1579
Merged
Conversation
…lies) (#1577) 3.7.0 wraps user opts.presets so DEFAULT_SITEMAP_OPTIONS (lastmod from git mtime, drops priority + changefreq) deep-merges into the classic preset's sitemap key. After this bump the site's sitemap.xml will finally ship <lastmod> tags on every URL, which is the single sitemap-level signal Google still uses for recrawl priority. The validator's lastmod check also flipped back to hard-fail in this release, so deploys regression-test the contract automatically.
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.
Replaces #1578 which conflicted on docs/package-lock.json (documentation had 3.6.2, development had 3.7.0). Resolved by taking development's lockfile, which is the newer + intended state.