Tests were failing before because the migration guide mistakenly mentions axon-config-jakarta, whereas it should be axon-configuration-jakarta. Another reason to automate.. @smcvb
https://docs.axoniq.io/reference-guide/axon-framework/upgrading-to-4-7#steps-to-upgrade-from-jakarta-to-jakarta

Tests were failing before because the migration guide mistakenly mentions axon-config-jakarta, whereas it should be axon-configuration-jakarta. Another reason to automate.. @smcvb https://docs.axoniq.io/reference-guide/axon-framework/upgrading-to-4-7#steps-to-upgrade-from-jakarta-to-jakarta

Thanks for the concern, @timtebeek.
Know that tooling like this is not "not" in place for a lack of desire but rather a matter of focus.
If our resources would allow it, this would've been in place already.

All the better that you're providing a pull request for the matter.
It is an open-source project, after all.

So, thanks for doing this, @timtebeek :-)

You're welcome; just happy to help, and with the initial module in place it's not that hard to maintain I would say.

No idea how to resolve the final check failure; will you take it from here?

Error: Input required and not supplied: github-token

Applied the first round of suggestion and answered a couple of questions, any other comments will have to wait until after work. You're welcome to push changes too, just so you know! :)