hotfix: sitemap lastmod fix + hold solana-tx-landing-latency off main - #605
Merged
Flotapponnier merged 2 commits intoJun 21, 2026
Merged
Conversation
Sitemap runs on force-dynamic (to bypass Next's 2 MB Data Cache limit on the rendered output), which means `new Date()` at module init re-evaluates on every Google crawl. Effect: every URL had a freshly updated <lastmod> each visit, Google flagged the signal as unreliable sitewide and stopped using lastmod for recrawl prioritisation (confirmed behaviour, documented by Gary Illyes publicly). Fix: bake a build-time timestamp via next.config env injection, read it from process.env.NEXT_PUBLIC_BUILD_TIME in sitemap.ts. Stable per deploy, fresh per deploy. Per-bench <lastmod> still uses live bench.lastRunAt as before — that path was already correct.
Bench and its dependent /alternatives + /answers pages held off main while the harness data quality / methodology is iterated on dev. Matches the existing release-hold pattern (see 12bb8a7). Files stay on dev untouched; dev to main merges will need to re-delete or skip. Removed: - benchmarks/solana-tx-landing-latency.yml - alternatives/jito.yml (benchmark: solana-tx-landing-latency) - alternatives/helius.yml (benchmark: solana-tx-landing-latency) - answers/which-solana-rpc-lands-the-most-transactions.yml
Uh oh!
There was an error while loading. Please reload this page.
Flotapponnier
deleted the
hotfix/sitemap-lastmod-and-hold-solana-tx-landing
branch
June 21, 2026 12:01
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 freeto 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.
Two changes, both main-only:
Cherry-pick of dev fix(sitemap): pin <lastmod> to deploy time, not request time #604 — pin sitemap to deploy time instead of request time so Google trusts the freshness signal again.
Hold solana-tx-landing-latency bench off main (same pattern as 12bb8a7): removes the bench YAML + its 2 dependent /alternatives entries + 1 /answers page. Bench stays on dev untouched; harness data quality is being iterated. Files will need to be re-deleted or skipped on the next dev to main merge.