docs: update file versioning matrix for 2.2 rollout#6033
Merged
Conversation
Contributor
Review SummaryDocumentation-only change - LGTM ✓ No P0/P1 issues identified. The version matrix update and alias clarifications are clear and accurate. One very minor nit (not blocking): The last table row is missing a space before the closing vs the consistent style in other rows: This can be fixed in this PR or a follow-up, but it's purely cosmetic. |
BubbleCal
approved these changes
Feb 27, 2026
wjones127
pushed a commit
to wjones127/lance
that referenced
this pull request
Mar 4, 2026
The versioning doc still reflected a 2.1-era matrix and hard-coded `stable` / `next` descriptions, which could become stale and confusing during 2.2 rollout. --- **Parts of this PR were drafted with assistance from Codex (with `gpt-5.3-codex`) and fully reviewed and edited by me. I take full responsibility for all changes.**
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
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 versioning doc still reflected a 2.1-era matrix and hard-coded
stable/nextdescriptions, which could become stale and confusing during 2.2 rollout.Parts of this PR were drafted with assistance from Codex (with
gpt-5.3-codex) and fully reviewed and edited by me. I take full responsibility for all changes.