Backport promote tracking api #2432
Closed
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
ruhan1
force-pushed
the
2.7.x-backportpromotetrackingapi
branch
from
1487b7d
to
33f157d
Compare
|
2.7.x is not good place for this backport. Close this and use 2.5.4.x branch. |
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.
PNC was using indy-client 2.5.4 and tried to update to 3.3.x but failed due to CDI issues. They will file a Jira for that.
After talking, we decided to backport the needed promote api to old indy-client. Indy 2.5.x is too old, the 2.7.x seems a better place. So I backported the api to 2.7.x. PNC can use it as a quick fix.
PS. This pr also add the github actions to build and push the snapshot to sonatype.