Increment version for keyvault releases #22639
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
azure-sdk
requested review from
JimSuplizio,
alzimmermsft,
backwind1233,
chenrujun,
danieljurek,
g2vinay,
mitchdenny,
samvaity,
saragluna,
stliu,
vcolin7 and
yiliuTo
as code owners
ghost
added
Member
|
@backwind1233 @chenrujun We need to merge these increment PRs that are created after a release. In this case, this one corresponds to the release of JCA earlier this week. |
Member
|
/check-enforcer evaluate |
Member
|
/check-enforcer override |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Increment package version after release of com.azure azure-security-keyvault-jca