I have not been able to identify any other parties manually installing anything on the environment. This is not a multi-tenant solution, so there should not be any conflicts there. I am continuing to look into the issue, but have not identified any fixes yet.

These logs are from an attempt to build the project when the core.wcm.components packages are in the odd state Log file /aem/crx-quickstart/logs/error.log 14.06.2024 16:06:05.074 *INFO* [qtp1844516416-55920] com.day.crx.packaging.impl.SlingInstallerSupportImpl Sling installer node /system/sling/inst...

Yes, here are the pom.xml snippets /pom.xml<core.wcm.components.version>2.23.4</core.wcm.components.version><dependency> <groupId>com.adobe.cq</groupId> <artifactId>core.wcm.components.core</artifactId> <version>${core.wcm.components.version}<...

We define the core component version in our pom.xml in the project's base directory.<core.wcm.components.version>2.23.4</core.wcm.components.version>I also thought this could have been the issue, but we have cleared out all other versions of core.wcm.components from the instances and are experiencin...

Service Pack: 6.5.20core.wcm.components: 2.23.4Instances Affected: Author and Publish We noticed that our ui.content and ui.apps packages would sometimes not automatically install themselves through our normal pipeline and we had to install them after a code build manually.  We were able to identify...