|
|
|
|
|
by kubanczyk
1000 days ago
|
|
> 4. docker-compose has introduced breaking changes in its history ...until the point when they resigned any notion of versioning. You can't have a breaking change if you don't promise a stable behavior, see? /s Not many people noticed that the top-level version "3.9"
has no effect anymore. "It is only informative", the current spec says. Your old docker-compose.yaml files spew errors as soon as they go out-of-sync with the master branch (classy!) of the spec repo. |
|