docs-site: bring the published version list current to v0.6#44
Merged
Conversation
The Pages site hardcoded its version list at v0.4 in three places: generate.mjs VERSIONS, .gitignore, and index.md. The "latest" page already rendered v0.6 content but was mislabelled "v0.4", and v0.5/v0.6 were missing from the version dropdown and snapshots (v0.5 drift predates the icon work). - generate.mjs: latest → v0.6; add v0.5 (2c1f83e) and v0.4 (50985f5) as pinned snapshots; note the list is hand-maintained per version bump. - .gitignore: replace the enumerated v0.1…v0.4 with a `v[0-9]*/` glob so the ignore list can't drift again. - index.md: hero "v0.1 through v0.4" → "v0.1 through v0.6". Verified: `node scripts/generate.mjs` writes 6 version pages, versions.json has 6 entries, latest banner reads v0.6. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 participants
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.
Why
The Pages site hardcoded its version list at v0.4 in three places, so it drifted:
/latest/already rendered v0.6 content but was labelled "v0.4 (latest)", and v0.5 + v0.6 were missing from the Versions dropdown and the browsable snapshots. (The v0.5 gap predates the icon work —visual-specwas bumped to v0.5 in #31 without updating the site list.)What
generate.mjs—latest→ v0.6; pin v0.5 (2c1f83e) and v0.4 (50985f5) as reconstructed snapshots; note the list is hand-maintained per version bump..gitignore— replace the enumeratedv0.1…v0.4with av[0-9]*/glob so the ignore list can't drift again.index.md— hero "v0.1 through v0.4" → "v0.1 through v0.6".Verified
node docs-site/scripts/generate.mjs→ 6 version pages,versions.jsonhas 6 entries (v0.6 latest … v0.1), latest banner reads v0.6.Follow-up (not in this PR)
The version list is still hand-maintained in two files. A small auto-discovery refactor (derive versions by parsing
Version X.Y —fromgit logofvisual-spec.md) would remove this drift class entirely — worth a separate issue.🤖 Generated with Claude Code