In our case, the server we're deploying to is running some older version of jackrabbit oak-core: 1.22.13. This issue looks like it was introduced in 1.56.0, which means somehow the cloud pipeline is scanning against the latest versions of packages that don't even apply to the server that's being dep...

Can the AEM code quality pipeline be fixed to not randomly fail builds due to new issues it finds with existing dependency packages that haven't been changed since the last build?