Description

Bringing a container up using a combination of the --force-recreate and --no-deps flags consistently leads to "no such service" errors for dependent services of the target service.
This works without problems with 2.4.1 but not in 2.5.0.

Steps to reproduce the issue:

1. docker compose up -d --force-recreate --no-deps SOME_SERVICE

Describe the results you received:
"no such service: some-dependent-service"

Describe the results you expected:
Container to be recreated and started without errors

Additional information you deem important (e.g. issue happens only occasionally):
Issue happens consistently with 2.5.0 but doesn't happen with 2.4.1.

Output of docker compose version:

Docker Compose version v2.4.1