Hi everyone,
I just updated the org.axonframework.axon-bom to version 4.12.1, which is currently the latest according to the Axon BOM repository.
However, after upgrading, I’m seeing messages like:
AxonIQ has found the following dependency upgrade(s):
2025-11-17 09:41:58 [Thread-1] INFO o.a.u.LoggingUpdateCheckerReporter -
org.axonframework:axon-spring................................. 4.12.1 -> 4.12.2
etc.
It looks like the BOM lags behind the individual Axon module releases. That’s a bit unfortunate, because I rely heavily on the BOM to keep everything aligned.
On our acceptance and production environments, outgoing connections are blocked. As a result, we also get a lot of log entries like:
"message": "Failed to report anonymous usage data. Received status code: 400",
"logger_name": "org.axonframework.updates.UpdateCheckerHttpClient",
Given all of this—and because we already have our own internal processes for tracking updates—I’d like to disable Axon’s update check completely.
Our configuration is fully centralized in application.yml files (global + per-environment). But according to the documentation (Axon Framework Update Checker), it looks like disabling the update checker cannot be done through YAML configuration. I tried several properties, derived from the documented ones but was not able to disable the check.
Does anyone know a clean way to disable the update checker while keeping all configuration inside application.yml?
The ‘best’ solution I could think of is to excluded the UpdateCheckerAutoConfiguration in the @SpringBootApplication, but any advice or other workarounds would be greatly appreciated!
Thanks,
Frank