docs: restore the compatibility CI milestone wording - #18
Merged
Conversation
Rebasing the supervisor branch reverted this line to its pre-compatibility text, so the roadmap claimed compatibility CI was still outstanding while it ran on every build, including the 0.8.0 release. The Implemented and tested entry survived the rebase; only the milestone regressed.
Greptile SummaryThis documentation-only PR restores accurate compatibility-CI milestone wording.
Confidence Score: 5/5The PR appears safe to merge with no actionable issues identified. The revised roadmap wording agrees with the compatibility workflow and the document’s explicit supported-matrix description. Important Files Changed
Reviews (1): Last reviewed commit: "docs: restore the compatibility CI miles..." | Re-trigger Greptile |
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.
Milestone 7 on main claims compatibility CI is still outstanding. It shipped in #17 and runs on every build, four cells, including the v0.8.0 release job.
I wrote this correction in #17 and then reverted it myself: rebasing #16 onto main resolved the
CHANGELOG.mdconflicts but silently restored my branch's older copy ofdocs/roadmap.md. The "Implemented and tested" entry survived; only the milestone line regressed.Two lines, restoring what #17 said, including that Ruby 4.0 is still absent from the matrix.
Documentation only. No version bump.