Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump jackson and snakeyaml dependencies #676

Closed
Tracked by #168
owaiskazi19 opened this issue Sep 29, 2022 · 5 comments
Closed
Tracked by #168

Bump jackson and snakeyaml dependencies #676

owaiskazi19 opened this issue Sep 29, 2022 · 5 comments
Labels
enhancement New feature or request v2.4.0

Comments

@owaiskazi19
Copy link
Member

owaiskazi19 commented Sep 29, 2022

Is your feature request related to a problem?
Core has bumped jackson and snakeyaml dependencies here to 2.13.4 and 1.32 respectively for versions 2.x, 2.3 , 2.2 , 2.1 , 2.0, 1.3 and 1.x. Plugin and client teams should do the same to align with core.

What solution would you like?
A clear and concise description of what you want to happen.

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

@amitgalitz
Copy link
Member

amitgalitz commented Oct 10, 2022

Is this not required for 2.3.1? @minalsha

@owaiskazi19
Copy link
Member Author

Is this not required for 2.3.1? @minalsha

@amitgalitz core has updated the dependencies for the above versions mentioned (2.x, 2.3 , 2.2 , 2.1 , 2.0, 1.3 and 1.x). So it's better to keep the plugins on the same version to avoid the conflict.

@bbarani
Copy link
Member

bbarani commented Oct 12, 2022

@amitgalitz We are currently not looking to do 2.3.1 release but it might change if we end up fixing any critical patches in 2.3.0 release. Can you please let us know the plan for 2.4.0?

@amitgalitz
Copy link
Member

This fix has been backported too 2.x so will be a part of the 2.4.0 release.

@amitgalitz
Copy link
Member

Closing this issue as we backported the change to future potential 2.3.1, 2.4.0, 1.3.6 releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v2.4.0
Projects
None yet
Development

No branches or pull requests

5 participants