-
Notifications
You must be signed in to change notification settings - Fork 39
Release 1.5.5 #265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Release 1.5.5 #265
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
WordPress core sitemaps (introduced in WP 5.5) use the same 'sitemap' query var as MSM Sitemap. When core's sitemap handler runs and finds no matching core sitemap, it sets a 404 status. Even though MSM Sitemap outputs valid XML with the correct Content-Type header, the 404 status persists because we only set headers for Content-Type, not the HTTP status. This causes search engines to receive a 404 status with valid sitemap content. By explicitly calling status_header( 200 ) before outputting the XML, we override any previously set status and ensure search engines receive the correct 200 OK status with our valid sitemap content. This approach is cleaner than the current VIP Go workaround in vipgo-helper.php which disables core's render_sitemaps action entirely.
Bumps the dev-dependencies group with 1 update: [@wordpress/env](https://github.com/WordPress/gutenberg/tree/HEAD/packages/env). Updates `@wordpress/env` from 10.36.0 to 10.37.0 - [Release notes](https://github.com/WordPress/gutenberg/releases) - [Changelog](https://github.com/WordPress/gutenberg/blob/@wordpress/env@10.37.0/packages/env/CHANGELOG.md) - [Commits](https://github.com/WordPress/gutenberg/commits/@wordpress/env@10.37.0/packages/env) --- updated-dependencies: - dependency-name: "@wordpress/env" dependency-version: 10.37.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dev-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
…ependencies-41c662f996
Changes get_post_modified_time() from GMT (true) to site timezone (false) for consistency with the sitemap index fix in #248. Affected files: - SitemapIndexEntryFactory::from_post() - UrlEntryFactory::from_post() This ensures all lastmod dates in sitemaps use the site's configured timezone, preventing incorrect UTC timestamps that could cause search engines to flag dates as invalid. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Per Google's sitemap specification, the lastmod value in a sitemap index should indicate when the sitemap file was last modified, not the date the sitemap represents. Previously, a sitemap for 2024-01-15 would show lastmod as 2024-01-15T00:00:00. Now it correctly shows when the sitemap was regenerated (e.g., 2025-12-30T07:01:33). Changes: - Touch sitemap posts when regenerating to update post_modified - Query both post_date (for URL) and post_modified (for lastmod) - Factory now accepts optional modification time mapping This helps search engines understand which sitemaps have actually changed and need re-crawling. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
WordPress automatically sets posts with future dates to 'future' status instead of 'publish'. The test was using June 15th of the current year, which fails in the first half of the year when that date is still in the future. Changed to use January 1st of the current year, which is always in the past regardless of when the test runs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
561a66b to
34ffa98
Compare
34ffa98 to
29f0a89
Compare
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.
Summary
Bugfix release focusing on sitemap lastmod date accuracy and HTTP response handling.
Fixed
post_modifiedfor sitemap index lastmod values (#262)Maintenance
.npmrcfor npm configurationPlanned release date: 6th January 2026
🤖 Generated with Claude Code