Only validate upper bound of current branch on release branches #135391
+30
−5
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
When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
rjernst
added
:Core/Infra/Core
elasticsearchmachine
added
Team:Core/Infra
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
jdconrad
approved these changes
Sep 25, 2025
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 25, 2025
…tic#135391) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
This was referenced Sep 25, 2025
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 25, 2025
…tic#135391) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 25, 2025
…tic#135391) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 25, 2025
…tic#135391) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 25, 2025
) (#135466) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
rjernst
added a commit
that referenced
this pull request
Sep 25, 2025
) (#135465) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 25, 2025
) (#135468) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
rjernst
added a commit
that referenced
this pull request
Sep 26, 2025
) (#135467) When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.
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.
When transport version changes are backported they may carry along multiple upper bounds files that have been updated. Yet in release branches the only upper bound file that matter is that of the current branch. This commit adjusts validation on release branches to only check the current upper bound file.