Unclear version compatibility notice in Discloud output

When running Discloud commands, users sometimes see a message that indicates a version compatibility issue. The goal is to determine what specific version comparison triggers this notice and what it means for the operation being performed.

Because public documentation for Discloud does not describe an explicit version‑compatibility check, the exact criteria and thresholds remain uncertain. Understanding whether the notice reflects a hard block, a warning, or an informational cue is important for troubleshooting and automation.

What version components does Discloud compare when emitting the compatibility notice? Under what conditions is the notice suppressed or escalated? Does the notice represent a hard incompatibility or merely a warning?