"Dependabot" for the Quarkus Platform

[Guillaume Smet]

Hi,

Yesterday, I teamed up with Claude Code to do something I never had the time to do: have some sort of Dependabot for the Quarkus Platform.

===

Why do we need our own?

The Platform is specific as we don't want to update the dependencies but the Platform members so we need to scan the parent looking the the Platform members and their version, then update only the parent and run `./mvnw -Dsync` to sync the Platform.

===

It created its first PR today: https://github.com/quarkusio/quarkus-platform/pull/1832/changes .

Nice it was the MCP Server as it was Martin K. complaining the most about it :)

We will probably have to improve it over time but it could already be helpful.

I excluded Quarkus CXF and Camel Quarkus for now.

I'm hesitant for Quarkus Operator SDK as I know Chris has its own automation but this one can differentiate all updates for main and micro updates for back branches, which might be handy.

Chris, let me know what you think.

If you prefer keeping your own automation, no biggie for me.

Config file is here:

https://github.com/quarkusio/quarkus-platform/blob/main/.github/update-quarkus-platform.yml

(we have the ability to override the policy for each branch/member if necessary)

Action is here:

https://github.com/quarkusio/update-quarkus-platform-action

(code might not be perfect, I'll review it more closely at some point...)

HTH

-- 

Guillaume

[Guillaume Smet]

On Thu, Mar 26, 2026 at 11:09 AM 'Andy Damevin' via Quarkus Development mailing list <quark...@googlegroups.com> wrote:

Awesome! I remember having out of sync qute-web in there

Ah good thing you mention Qute Web as it made me realize I was only analyzing the members and not the elements defined in the core dependency management section.

This should now be handled properly. 

[Max Rydahl Andersen]

Cool stuff - I reckon Dependabot/renovatebot will still be relevant for the non-quarks platform updates?

Is there a config that should be set to avoid double prs ?

/max

--
You received this message because you are subscribed to the Google Groups "Quarkus Platform Coordination" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-platform-coo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-platform-coordination/CALt0%2Bo8kg-162X4WsyOOUfEDb9L3FqG_Mt97-puPNocepFoFyA%40mail.gmail.com.

[Jan Martiška]

This is one big awesome, thanks for this!

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo8kg-162X4WsyOOUfEDb9L3FqG_Mt97-puPNocepFoFyA%40mail.gmail.com.

[Georgios Andrianakis]

I didn't get this at first, but seeing is believing and now I know it's great!

You received this message because you are subscribed to the Google Groups "Quarkus Platform Coordination" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-platform-coo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-platform-coordination/CAD8__OHb2U02nbQeNA5JBKFVeBkny49x7-%3Da9Vdp-WOcSsH%2B3Q%40mail.gmail.com.