[docs-scanner] FAQ doesn't mention Compose v5

[docker-agent]

File: content/manuals/compose/support-and-feedback/faq.md

Issue

The FAQ "What is the difference between docker compose and docker-compose" explains the history of Compose v1 (2014) and v2 (2020), but doesn't mention Compose v5, which was released in 2025 according to the documentation.

From faq.md:

Version one of the Docker Compose command-line binary was first released in 2014. It was written in Python, and is invoked with docker-compose. Typically, Compose v1 projects include a top-level version element in the compose.yaml file, with values ranging from 2.0 to 3.8, which refer to the specific file formats.

Version two of the Docker Compose command-line binary was announced in 2020, is written in Go, and is invoked with docker compose. Compose v2 ignores the version top-level element in the compose.yaml file.

However, the sibling file content/manuals/compose/intro/history.md states:

Compose v5, released in 2025, is functionally identical to Compose v2. Its primary distinction is the introduction of an official Go SDK.

And:

Today, the supported Docker Compose CLI versions are Compose v2 and Compose v5, both of which are defined by the Compose Specification.

Why this matters

Readers who have seen references to Compose v5 elsewhere in the documentation (or in release notes, blog posts, etc.) will be confused when the FAQ only mentions v1 and v2. They may wonder:

• Is v5 a different thing entirely?
• Is the FAQ outdated?
• Should they be using v2 or v5?

The FAQ is often the first place users look for clarification, so it should reflect the current state of the product.

Suggested fix

Update the FAQ answer to acknowledge Compose v5. Since v5 is "functionally identical to Compose v2" (per history.md), the FAQ could add a brief note like:

Version two of the Docker Compose command-line binary was announced in 2020, is written in Go, and is invoked with docker compose. Compose v2 ignores the version top-level element in the compose.yaml file.

Note: Compose v5, released in 2025, is functionally identical to v2 and also uses docker compose. The main difference is the introduction of an official Go SDK. For most users, v2 and v5 behave the same way.

Or simply add a sentence at the end:

Compose v5 (released in 2025) is functionally identical to v2 for most users; see History and development of Compose for details.

---

Found by nightly documentation quality scanner