Two dated items in Adobe’s current AEM as a Cloud Service release notes can’t be postponed: the Java 25 runtime timeline (optional enablement from November 2026, lower environments from February to May 2027, all runtimes in June 2027) and the enforcement of deprecated Java API removals, where the cutoff for critical updates has already passed. This post summarizes the dates and the 14 packages Adobe lists, shows how Adobe says to find usages with the AEM Analyser Maven Plugin, and points out where Adobe’s own pages disagree, so you know what to confirm for your environments.

Most AEM privacy incidents aren’t sophisticated breaches they’re a testimonial copy-pasted straight from a support ticket with a real customer’s name and email still in it, published because nobody built a check assuming it needed one. This post shows how pre-publish PII scanning (both pattern-based and contextual), component-level consent tagging gated against live CMP state, and automated privacy-policy alignment checks catch these gaps before publish with every flag routed to a human privacy owner, never resolved automatically.