[BUG] I was testing this issue using the latest ci artifacts (https://github.com/docker/compose/actions/runs/8063698832) and stumbled upon a regression

[luciangabor]

          I was testing this issue using the latest ci artifacts (https://github.com/docker/compose/actions/runs/8063698832) and stumbled upon a regression

here's my setup:

$ find -name '*.yaml' -print -exec cat {} \;
./compose.yaml
include:
  - path:
      - dir/included.yaml
./dir/included.yaml
services:
  service:
    extends:
      file: extended.yaml
      service: service
./dir/extended.yaml
services:
  service:
    build: .

the regression is about running compose from a different dir:

$ docker compose version
Docker Compose version e2762b1

$ find
.
./compose.yaml
./dir
./dir/included.yaml
./dir/extended.yaml

$ docker compose config
name: attach
services:
  service:
    build:
      context: /path/to/attach/dir
      dockerfile: Dockerfile
    networks:
      default: null
networks:
  default:
    name: attach_default

$ env -C dir docker compose config
cannot read extended.yaml

Originally posted by @luciangabor in #11529 (comment)

[luciangabor]

seems to be fixed

ups, nope

[luciangabor]

it's part of 2.24.7 now