Repository navigation
fix(landing): sweep the version stamps the rc.87 roll missed - #1206
Merged
Merged
Conversation
The rc.86 release commit (baada0a) carried the landing stamp sweep inline; the rc.87 roll (PR #1203) stamped engine/Cargo.toml and Cargo.lock but not the landing pages, so the Landing constants guard fails on main: 91 V1.0.0-RC.86 stamps (plus the data-latest-tag fallback in landing/index.html) against the tree's 1.0.0-rc.87. Mechanical sweep only, no prose touched: V1.0.0-RC.86 -> V1.0.0-RC.87 across landing/, and the one lowercase v1.0.0-rc.86 data-latest-tag span. The llms.txt 'Current release' check was already green (it reads the engine version), which is why only this guard went red. Files: 55 landing pages, one line each (print headers + footers).
The stamp sweep (previous commit) touched 55 landing pages, so every lastmod in landing/sitemap.xml moved; the Technical SEO gate on PR #1206 caught the staleness. Regenerated with scripts/seo/gen_sitemap.py --write: 183 URLs, no URL set changes, dates only.
Merged
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Oct 10, 2026
Cite xerj-org#1205 on the --code-analyzer entry (the maintainer rebase PR has no closing-issue link; auto-close fired from the merge commit), add the xerj-org#1206 landing-stamps entry, and mark the xerj-org#1183 entry as the read-back half with the issue open pending the live rebuild.
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Oct 10, 2026
The xerj-org#1206 entry lives inside the rc.88 section, so "the rc.88 roll below follows" pointed at itself. Says what this roll did instead.
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
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.
Main is red: the rc.86 release commit (baada0a) carried the landing stamp sweep inline, but the rc.87 roll (PR #1203) stamped engine/Cargo.toml and Cargo.lock only. 91 V1.0.0-RC.86 stamps (plus the lowercase data-latest-tag fallback in landing/index.html) now sit against a tree that calls itself 1.0.0-rc.87, and the Landing constants guard fails on main — which also blocks PR #1205, whose only failure is this same job.
Mechanical sweep, no prose touched: V1.0.0-RC.86 → V1.0.0-RC.87 across landing/, one line each in print headers and footers, plus the single lowercase span in landing/index.html.
Process fix follows separately: the release roll checklist gets the landing sweep as an explicit step so rc.88 cannot repeat this.