Version 0.25.0

[jonasvoelcker]

Hey @tchiotludo,

we did some checks against our DEV-Cluster and found out that the current dev-Branch performs way better than version 0.24.0, might it be possible to release the current version soon?

Best Regards
Jonas

[AlexisSouquiere]

I agree too. And it's a huge one 😄
I think PR #1650, #1654 and #1655 should be merged first but on my side I don't see any blocking bugs remaining that is preventing a release.

[jonasvoelcker]

Hey @tchiotludo,

thanks a lot for taking that bunch of time and even if we push you here we are really greatful for your work :)

[raphael-afanyan]

Hi @tchiotludo, thanks for all the work you are doing, can we expect a new version soon?

[yanntoque]

Hello,
Any news about a release date for the 0.25.0, i can't image the work behind it.
I'm not here to complain, but as we use your solution in 0.24.0 (released on April 2023) and there are a bunch of CVEs.
We are sadly thinking about using another solution to mitigate those CVEs to be compliant.

[AlexisSouquiere]

@yanntoque the PR #1678 is in its final stage. Development is completed. I deployed it in my company on a panel of users to get feedback. If there is no blockers in the coming days I will mark it as ready and then release can be done quickly. I would still recommend to let people try the dev branch for a week or two and see if we didn't miss anything.
Anyway, feel free to contribute to fix the CVEs in the future ;)

[jonasvoelcker]

Hey @yanntoque,

we are still busy tackling the frontend rework to resolve many of those CVEs. @AlexisSouquiere just started to test the version we prepared on their dev cluster. I did also manage to check the basic functions against our Dev Kafka.

Do you mind checking out our branch and providing your feedback? :)

#1678

Best Regards
Jonas

[jonasvoelcker]

Hi @tchiotludo, do you maybe have some checklist what needs to be done before releasing? Maybe some of us could add some value but I guess nobody knows, what's in your mind ;)

[tchiotludo]

@jonasvoelcker, we have someone really motivated to work on the UI upgrade, it's something really valuable, and thanks @AlexisSouquiere to take the subject.
I already looked month ago, and the work amount is really huge but it needed to be done. AKHQ is used in large corporate with CVE scanner, and there is a lots because of the frontend, If we can remove this one, all the community will be happy.
I know that delayed a release can be painful but I think it's not a pain to wait some weeks more.
At the end, this release will be the biggest one and thanks to @AlexisSouquiere for large parts.

[AlexisSouquiere]

And also to @jonasvoelcker who is the one helping me (and did a loooot) on the UI upgrade 😉

[shaneikennedy]

@tchiotludo or @AlexisSouquiere Any chance there's a checklist of what's left before release? Happy to help out 🙂

[jonasvoelcker]

Hey @shaneikennedy,

we just managed to merge all the stuff together today. So there will not be much left, I think.

What I do not understand is the failing action in the Main-Workflow:

cp: target 'build/distributions/akhq.tar' is not a directory

If you would find a solution for that, it would be really great 😉

[shaneikennedy]

#1702

it was me who broke it ! definitely revert my commit if that's all that's blocking a release 👍

[jonasvoelcker]

Unfortunately there is still at least this issue blocking the current version being released: #1704

It causes every local setup without enabled security to break.

[shaneikennedy]

How about now? Happy to help out if I can :)

[jonasvoelcker]

This one should also be merged: #1708

The dependabot changes can also be merged if @tchiotludo runs this command first:

@dependabot rebase

Afterwards we are ready to go in my opinion.

[tchiotludo]

@AlexisSouquiere @jonasvoelcker I've updated to latest dependencies yesterday.
Only the confluentVersion couldn't be updated (missing dependencies in kSQL, don't know why).
If you have time, you make a final review on the dev image, I will published the new version just after

[jonasvoelcker]

@tchiotludo Would you be so kind? 😃

[deibl]

Guess i might have to look for a new morning routine soon in the Future.
Fetch Coffee, Boot my Mac, Check if AKHQ 0.25.0 was released, proceed with my actual work.

[alwibrm]

@tchiotludo What do you think, are we ready to release 0.25.0?

[shaneikennedy]

@jonasvoelcker sorry for the slow reply i don't have my github notifcations setup well. I'd love to test this on our staging and testing clusters but we ship the akhq jar file that gets published on release, so I'd need an "official" release to do any non-trivial testing (without doing a ton of work, that is).

Happy to just release 0.25.0 and provide feedback and contributions as we test it, releasing doesn't mean everyone is forced to upgrade 👍

[jonasvoelcker]

@tchiotludo I agree with @shaneikennedy, nobody is forced to upgrade and even if we find new bugs that need to be fixed, there can easily be a version 0.25.1 soon. Is there anything which hinders you from releasing?

[theBNT]

Hi, the new release would also help the much anticipated JSON logging as described here PR #1772 <3

[alfsch]

It would be also fine to have a tagged pre-release which we could reference without using the dev tag.

[jonasvoelcker]

Eureka 😁