I found an inconsistency between the GitHub repository and the Go module artifact for:
github.com/compose-spec/compose-go/v2@v2.10.2
Repository (GitHub) behavior
ApplyInclude(...)
ApplyExtends(...)
Example:
https://github.com/compose-spec/compose-go/blob/v2.10.2/loader/loader.go
Go module artifact behavior
The module fetched via Go (proxy.golang.org) still contains the old order:
ApplyExtends(...)
ApplyInclude(...)
Verified via:
https://proxy.golang.org/github.com/compose-spec/compose-go/v2/@v/v2.10.2.zip
and local module cache:
$GOMODCACHE/github.com/compose-spec/compose-go/v2@v2.10.2/loader/loader.go
Impact
This causes include + extends inheritance to still fail when consuming the module:
docker/compose fails with the module artifact
- the same code works when using a local checkout (
replace => ../compose-go)
Summary
- GitHub tag
v2.10.2 → fixed behavior
- Go module artifact
v2.10.2 → old behavior
So the module content does not match the tagged source.
I found an inconsistency between the GitHub repository and the Go module artifact for:
Repository (GitHub) behavior
includebeforeextendsv2.10.2shows:Example:
https://github.com/compose-spec/compose-go/blob/v2.10.2/loader/loader.go
Go module artifact behavior
The module fetched via Go (proxy.golang.org) still contains the old order:
Verified via:
and local module cache:
Impact
This causes
include + extendsinheritance to still fail when consuming the module:docker/composefails with the module artifactreplace => ../compose-go)Summary
v2.10.2→ fixed behaviorv2.10.2→ old behaviorSo the module content does not match the tagged source.