cc @dperny

Codecov Report

Merging #4593 (af75b49) into master (dcc1610) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4593      +/-   ##
==========================================
+ Coverage   59.71%   59.72%   +0.01%     
==========================================
  Files         288      288              
  Lines       24858    24862       +4     
==========================================
+ Hits        14843    14850       +7     
+ Misses       9128     9126       -2     
+ Partials      887      886       -1     

docker/cli should not define some 3.10+ schema for compose file format, as this schema is maintained by https://github.com/compose-spec/compose-spec. This looks like some unofficial, unmaintained compose format fork, which deserve adoption of recent compose file features. Changes introduced by this schema could easily be supported by just adopting compose-go for compose file parsing, in replacement for the legacy parser.

The official v3 compose specification has always been maintained in this repository; compose happened to have a copy in its repository, and the compose-spec was forked from that.

compose file v3 indeed used to be maintained here, but this was before we (Docker) announced compose specification 4 years ago
compose-go indeed was forked from this code, then improved and partially rewritten. This should make it easier to adopt compose spec without much efforts, vs spending energy maintaining a distinct implementation