Update pins corresponding to 26.05#11
Draft
r-burns wants to merge 1 commit into
Draft
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
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.
Update pins to the baseline commit to which the patchset has been rolled forward, in #10. (Separate PR so that the backported
git ampatches are separate from manual changes.)Currently marked as draft as this PR would not be valid to merge without my other PRs (#9, #10).
Conversely, merging those branches before this one would leave the pins invalid on the commit prior to this merge - so my local working reference I'm using for 26.05 testing is an octopus merge of all three of these branches. I'll leave it up to you as to whether that's splitting hairs ;)