Repository navigation
docs(roadmap): say the Floe and Thaw roadmaps cover the next year - #19
diazdesandi wants to merge 1 commit into
Conversation
Signed-off-by: René Jiménez <diazdesandi@proton.me>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Strix Security Review✅ No open security findings. PR summary: Updates the Floe and Thaw roadmap pages so each one states its plan covers the next year, while keeping the existing "not a promise" wording. Review summaryBoth changed files are MDX documentation prose. The PR adds the words "for the next year" to a sentence in the Floe roadmap and the Thaw roadmap, to satisfy the OpenSSF Review 1 on this PR · Reviewed by Strix |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 25 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
Not needed: the website already handles this. |
The Floe and Thaw roadmaps now say they are the plan for the next year. The sentence stays "not a promise", and no item gets a date.
The OpenSSF Best Practices
documentation_roadmapcriterion asks for a roadmap covering at least the next year.Testing
content/site/floe-roadmap.mdxandcontent/site/roadmap.mdx.coderabbit review --agent: no findings.bun run lint,bun run types:checkand the smoke tests were not run.Other information
Claude Code (Claude Opus 5.5) found the sentence and made the edit.