[BUG] Combining include and secrets leads to validation errors when secrets are set environment variables

[lassebe]

Description

When defining a environment based secret in an "inner" compose file, compose reports a validation error.
However, this only occurs if the environment variable is actually set.

I would expect to be able to include compose files that define top-level environment secrets.
Hopefully I've just made some other mistake!

Steps To Reproduce

Tried to make this a minimal example.
Encountered in a situation with a service that actually references the secret, but given that it is blowing up earlier this should hopefully be sufficient to reproduce.

docker-compose.yml

include:
  - path:
      - ./app/docker-compose.yml

./app/docker-compose.yml

secrets:
  some-secret:
    environment: "MY_ENV_VAR"

If I run

export MY_ENV_VAR="anything"
docker compose config

I get the following error

validating /.../compose-test/docker-compose.yml: secrets.some-secret Additional property content is not allowed

If I then run

unset MY_ENV_VAR
docker compose config

It correctly returns a valid template

name: compose-test
services: {}

Similarly, running MY_ENV_VAR="anything" docker compose config inside app works perfectly, and outputs:

name: app
services: {}

Compose Version

docker compose version

Docker Compose version v2.29.2-desktop.2

docker-compose version

Docker Compose version v2.29.2-desktop.2

Docker Environment

Anything else?

No response

[ndeloof]

closing as a duplicate for #12033

[lassebe]

Ah, my bad, don't know how I missed that!