chore: bumped kafka-manager version #532
Conversation
updated patch level from 1.3.3.18 to 1.3.3.22
|
hi @brandonwittwer ! Thanks for noticing this. Our CI bot is a little unfriendly (we're still training it) and it requires the PR to be formatted in a precise way. We're reaching out to our release engineering team to see if we can merge your PR as-is. Otherwise we may have to close it and one of us will reformat it so that the merging bot won't complain. Stay tuned! |
|
Yeah, I noticed that. looks like the commitlint was happy with this one, but I had deleted one prior. Looks like this is just wanting a review sign-off |
ssalaues
changed the base branch from
development/1.1
to
feature/ZENKO-1543-kafka-manager-bump
|
@brandonwittwer Thanks for the contribution! I retargeted this PR to a trusted branch that our bot and CI will pick up and should get merged into development/1.1 later today here : |
|
That's awesome! Glad you could contribute and glad that the docker images are finding good use! 😃 |
Thanks @ssalaues. I think this was my first approved public github pull request. I'm officially an OSS dev 🥇 (with two keystrokes lol). I did this for a good reason though. You publish an image to hub.docker.com with the kafka-manager in it and this adds some compatibility updates. (had to delete other comment, wrong account.) |
updated patch level from 1.3.3.18 to 1.3.3.22
What does this PR do, and why do we need it?
kafka-manager patch 1.3.3.22 adds kafka 2.x support
Which issue does this PR fix?
fixes #
Special notes for your reviewers: