Repository navigation
docker-compose: Drop the obsolete version field - #1499
Merged
Merged
Conversation
Compose ignores the top-level version field, and has warned about it on every command since v2.25.0. Compose v1.29.0, the documented minimum, reads the files the same way without it.
michaellzc
approved these changes
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Compose ignores the top-level
versionfield, and has warned about it on every command since v2.25.0Solution
Remove
version: '2.4'from the five Compose files that had itChecklist
Test plan
configoutput matchesmainfor every file, on Compose v5.7.1 and v1.29.0 (the documented minimum), apart from theversionline that v1.29.0 prints. The v5.7.1 warning is gone