content: fix stale roadmap comment#26
Open
VijitSingh97 wants to merge 1 commit into
Open
Conversation
The roadmap comment said it was based on "the v1.1 / v2 milestones; rigforge v1.0 is fully closed", but the rendered roadmap below it now spans v1.1–v1.6 + v2 and both repos have forward milestones. Reword to match (Pithead drives the version themes, RigForge ships in lockstep). Non-rendered comment only — no copy, roadmap, or version-badge change. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
The non-rendered comment above
roadmap:indata/content.yamlwas stale: it described the roadmap as based on "the v1.1 / v2 milestones; rigforge v1.0 is fully closed", but the rendered roadmap right below it now spans v1.1–v1.6 + v2, and both repos carry forward milestones (RigForge's v1.1 tooling folds into the v1.5 release; stratum auth/TLS now lands in v1.5).Reworded to match reality (Pithead drives the version themes, RigForge ships in lockstep).
Scope: comment-only — no rendered copy, roadmap entries, or version badges change. YAML validates; nothing for htmltest to catch.
This was the only genuine inaccuracy found in a full pass over the site: the version badges (
data/releases.json) track actual releases so there's no phantom "RigForge v1.1", and the rendered roadmap/FAQ/project cards are all accurate as-is.🤖 Generated with Claude Code