doc-sync: fix second stale "in flight" tag for shipped v0.9.6-beta - #174
Draft
jacuzzicoding wants to merge 1 commit into
Draft
doc-sync: fix second stale "in flight" tag for shipped v0.9.6-beta#174jacuzzicoding wants to merge 1 commit into
jacuzzicoding wants to merge 1 commit into
Conversation
The road-ahead timeline in roadmap-to-v1.html still tagged v0.9.6-beta as "In flight today" even though it shipped 2026-05-27 (confirmed by the page's own top badge, version-history.html, and CHANGELOG.md). PR #173 already fixed the top badge but missed this second instance in the timeline milestone.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
public/roadmap-to-v1.htmlstill tags v0.9.6-beta as "In flight today" in the "road ahead" timeline (milestone section), even though it shipped 2026-05-27. The page's own top badge already says "Last shipped: v0.9.6-beta · 2026-05-27", andversion-history.html/CHANGELOG.md/docs/roadmap-to-v1.mdall agree it's shipped.The already-open draft PR #173 fixed the top badge instance of this same "in flight" drift but the timeline milestone tag is a second, separate occurrence it didn't touch.
Decisions
Kept the existing
milestone current/milestone-tag nowCSS classes as-is (still the most-recently-shipped item, reasonable to keep visually highlighted) and only corrected the text label, matching the "Shipped 2026-05-27" phrasing already used elsewhere on the same page — minimal correction, no scope creep.Test plan
CHANGELOG.md/docs/roadmap-to-v1.md.Generated by Claude Code