Portainer silently ignores Docker Compose secrets when version is 3.9 or higher

The goal is to confirm whether secrets defined in a Docker Compose file are actually created when a stack is deployed through Portainer using a Compose version string of 3.9 or newer.

The Portainer interface does not emit a warning about version incompatibility; any diagnostics appear only in the server or agent logs, which creates uncertainty about whether the secrets are omitted silently or simply not reported.

Does Portainer drop the secrets section entirely when the Compose version exceeds 3.8? Are the missing secrets visible only in the agent or server logs, and is there a way to surface this information in the UI? Can a version‑compatibility check be enabled to prevent silent misconfiguration?