porting guide 2.19: document range() changes #2832
Merged
Conversation
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
felixfontein
added
the
backport-2.19
Signed-off-by: Paul Arthur <[email protected]>
flowerysong
force-pushed
the
porting_2_19_range
branch
from
f5d6774 to
1a2538a
Compare
mattclay
approved these changes
Jul 22, 2025
samccann
approved these changes
Jul 23, 2025
Backport to stable-2.19: 💚 backport PR created✅ Backport PR branch: Backported as #2896 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Jul 23, 2025
Signed-off-by: Paul Arthur <[email protected]> (cherry picked from commit 0ff0517)
samccann
pushed a commit
that referenced
this pull request
Jul 23, 2025
(cherry picked from commit 0ff0517) Signed-off-by: Paul Arthur <[email protected]> Co-authored-by: flowerysong <[email protected]>
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.
This is noted in the changelog, but I think it's worth also calling it out in the porting guide (since that's where I expected it to be when I was trying to figure out if this was a bug.)