From 29b0142a47b6f16a25a8bee2f2bd7cd35b113779 Mon Sep 17 00:00:00 2001
From: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
Date: Thu, 12 Mar 2026 09:24:05 +0000
Subject: [PATCH] docs: address issue #24344
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This change was automatically generated by the documentation agent team
in response to issue #24344.

🤖 Generated with cagent
---
 content/manuals/compose/intro/history.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/manuals/compose/intro/history.md b/content/manuals/compose/intro/history.md
index f460f5f648..f5aab1d24f 100644
--- a/content/manuals/compose/intro/history.md
+++ b/content/manuals/compose/intro/history.md
@@ -41,7 +41,7 @@ Three major versions of the Compose file format for Compose v1 were released:
 - Compose file format 3.x with Compose 1.10.0 in 2017
 
 Compose file format 1 is substantially different to all the following formats as it lacks a top-level `services` key.
-Its usage is historical and files written in this format don't run with Compose v2.
+Its usage is historical and files written in this format don't run with Compose v2 or v5.
 
 Compose file format 2.x and 3.x are very similar to each other, but the latter introduced many new options targeted at Swarm deployments.