ci: remove docker-compose version top-level elements#6436
Merged
Xuanwo merged 1 commit intoapache:mainfrom Jul 19, 2025
Merged
Conversation
dosubot
bot
added
size:M
Xuanwo
approved these changes
Jul 19, 2025
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
2 participants
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.
Which issue does this PR close?
Closes #.
Rationale for this change
According to the Compose Specification, the top-level
versionfield in docker-compose files is obsolete and only kept for backward compatibility. Compose no longer relies on theversionfield to select a schema and will always use the most recent specification. Keeping theversionfield results in a warning message. Therefore, removing it aligns with the latest Compose specification.What changes are included in this PR?
Removed the top-level
versionfield from all docker-compose YAML files.Are there any user-facing changes?