Hello, I was talking with <@U08SLJK0YMD> yesterday...
# koog-agentic-framework
n
Hello, I was talking with @Anastasiia Zarechneva yesterday, and we agreed there is something we need to talk about. So here I share my original message:
What about having more frequent releases so we can grab fixes more often? As a maintainer too, I know when people have their PR merged they usually need it and are happy about having a release 😄
Koog is a great library; the only thing missing is regular updates so when things are fixed we can keep using the framework with the fixes. Having to wait more than a month after a PR is merged to be released is way too much I think. I don’t know what would be the correct way as you merge so many things everyday. As a maintainer I usually release when I merge a new fix (patch) or feature (minor) since I’m not getting PRs everyday. But on a that big library, maybe weekly updates can help. The world is evolving rapidly, and sometimes waiting a month for an update can change everything. Sure we can fork and use a local more up to date version, or publish it ourselves to a private maven repo, but most people won’t even try or know how to do this. Hope this can be discussed and evolve in the right way. And keep up the great work! 😉
kodee loving 3
a
Hi Nathan! Once you posted it, I remembered that we have a plan that might partly solve the problem: adding nightly builds (as was previously fairly proposed by Didier). While I realise it is not the classic releases, it might help with adopting some features earlier. WDYT?
👍 2
n
That would help because people could pick one of them to get fixes early. And if people want to wait for a more stable one they can wait for the normal release. Just a question: what would differentiate nightly from classic releases? Is it only the release frequency?
And also where would you plan to release them? Would they be on maven central with simply a different version number? Or maybe another repo dedicated versions so it’s not mixed with other official releases? (Yeah I know a lot of questions but this has to be done correctly to avoid issues and confusion)
a
Just a question: what would differentiate nightly from classic releases? Is it only the release frequency?
The frequency and the stability, I guess. As for the classic releases, we try to make features as reliable as we can, while testing nightly releases in a classic way can be a bit challenging 🥲
And also where would you plan to release them? Would they be on maven central with simply a different version number? Or maybe another repo dedicated versions so it’s not mixed with other official releases?
Let me summon someone from the team to answer this one, e.g. @Vadim Briliantov 🙂
n
I read on YouTrack that JB has a snapshot repository; so this might answer the question 🤷‍♂️
🙌 1
👍 1
s
> we try to make features as reliable as we can, while testing nightly releases in a classic way can be a bit challenging It's common to postfix a kind of incrementing to nightlies such that they are at least reproducible for a certain build. That way users can choose a specific version, its more akin to the current Grazie release. settings.gradle.kts, latest version
0.3.0.5
❤️ 1
d
That would be very welcome here - I am enjoying adopting Koog but am conscious that my App will only run at a competitive level of robustness and speed, with the Constrained Schema feature enabled; which is has been unreleased for a week or more now. All credit to the team for putting it together, Koog is growing quickly - I'm just saying I could certainly make use of nightlies to feel like I'm staying on top of my own Dev too, one less thing to come back to later.
👍 1
s
@darkmoon_uk you can check the link settings.gradle.kts and use
0.3.0.5
. It was published this week, and contains the schema feature.
kodee happy 1
🚀 2
d
Well isn't it my lucky day!? Cheers! 😂
n
Thanks @simon.vergauwen ; so is it already something working or is it still a manual release? But at lest having weekly manual builds is still better than having to wait a month for a fix
Well I cannot find the release on central, and the link you provided is a 404 for me. Did I miss something?
Image from iOS.jpg
s
It's available here, https://packages.jetbrains.team/maven/p/grazi/grazie-platform-public/ai/koog/koog-agents/ You need to setup JetBrains packages as a maven repository in Gradle, settings.gradle.kts
❤️ 2
n
Thank you, but I think the repo you’re sharing is private because I can’t open the GitHub link. Anyway adding a maven repo to a project is okay I can manage to do this 😆
s
I updated the links, can you try again?
❤️ 1
n
Thank you! Got it now
Nighly builds are now available: repositories { maven(url = "https://packages.jetbrains.team/maven/p/grazi/grazie-platform-public") } dependencies { implementation("ai.koogkoog agents0.4.1-develop-2025-09-01") }