Update revapi versions #44603
Merged
Update revapi versions #44603
+30
−30
Conversation
This file contains 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
billwert
requested review from
alzimmermsft,
samvaity,
g2vinay,
JonathanGiles,
rujche,
Netyyyy,
saragluna,
moarychan,
mssfang,
srnagar,
jeanbisutti,
trask,
ramthi,
heyams,
harsimar,
rajkumar-rangaraj,
joshfree,
a team,
anuchandy,
lmolkova and
vcolin7
as code owners
billwert
requested review from
maorleger,
pvaneck,
KarishmaGhiya,
scottaddie and
mpodwysocki
github-actions
bot
added
Azure SDK Tools
alzimmermsft
approved these changes
Mar 11, 2025
|
API change check API changes are not detected in this pull request. |
|
/azp run java - code-quality-reports |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - code-quality-reports |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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 revapi versions we were on include a CVE affected version of log4j. Updating moves past that.