What docker/compose shipped
Written by FoxPlug from the repository's own releases; not affiliated with Docker. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/docker/compose; Docker did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Compose reads Docker Hub credentials from the account signed in to Docker Desktop before falling back to the Docker CLI config file and its credential helpers. Pull request #14295
- Fixed a bug where a container that restarts while Compose is following its logs no longer prints the same log line twice. Pull request #14314
- The plan executor now runs start-phase operations such as waiting on a dependency's condition and running pre-start steps. Pull request #14274
- DownOptions.Images is now a typed ImagePruneMode validated upfront instead of a bare string validated only after containers were already removed. Pull request #14149
- An optional dependency whose health check wait is cancelled or times out is no longer reported as skipped. Pull request #14309
- Bridge commands now reject the --dry-run flag instead of silently ignoring it and performing real changes. Pull request #14307
- Removed a broken CONTRIBUTING.md link from the documentation. Pull request #14251
Why it matters
This week brings fixes and groundwork that affect everyday use: credentials for Docker Hub images now come from the Docker Desktop sign-in, restarting containers no longer duplicate log lines, and mistyped image prune modes fail before teardown begins. Progress on the plan executor also moves Compose toward running start-phase operations directly. Overall the week reduces surprising behavior and halves-finished operations for people using Compose.
Changelog entry
- Compose reads Docker Hub credentials from the Docker Desktop sign-in before falling back to the Docker CLI config file and its credential helpers. Pull request #14295
- Fixed duplicate log lines when a container restarts while logs are being followed. Pull request #14314
- DownOptions.Images is now a typed ImagePruneMode validated upfront. Pull request #14149
- A cancelled or expired wait on an optional dependency is no longer reported as skipped. Pull request #14309
- Bridge commands now reject --dry-run instead of silently ignoring it. Pull request #14307
- The plan executor now runs start-phase operations. Pull request #14274
- Removed a broken CONTRIBUTING.md link. Pull request #14251
This week in Compose: Docker Hub credentials now come from the signed-in Docker Desktop account, restarting containers no longer double-print log lines, DownOptions.Images is a validated type, optional dependency waits that are cancelled are no longer called skipped, and the plan
This week in Compose, several changes improve correctness for everyday use. Compose now reads Docker Hub credentials from the account signed in to Docker Desktop, before falling back to the Docker CLI config file and its credential helpers. A container that restarts while Compose follows its logs no longer prints the same line twice. DownOptions.Images is now a typed ImagePruneMode validated upfront, so a bad value fails before down removes containers rather than after. Optional dependencies whose health check wait is cancelled or hits its deadline are no longer reported as skipped. Bridge commands reject --dry-run instead of ignoring it. The plan executor now runs start-phase operations, and a broken CONTRIBUTING.md link was removed.
Week of September 28, 2026
What shipped
- V5.6.0 released with partial support for manually-triggered jobs; scheduled jobs will be added once Docker Engine support is available. Release
- Provider-backed services now participate in the image phase, allowing build and image declarations on provider services to reach the provider's runtime. Pull request #14252
- Provider relay links now get their own dedicated bridge network instead of relying on providers to guess bind addresses. Pull request #14275
- Fixed --dry-run hanging when services depend on others via
depends_onwithservice_completed_successfullycondition. Pull request #14270 - Pre_start hook containers are now first-class resources in the reconciliation plan, created by the plan rather than during the start phase. Pull request #14221
- Docker compose down --rmi no longer prints misleading dangling image removal messages when there's nothing to clean up. Pull request #14266
- Fixed compatibility with compose-go v2.16.1 which silently promotes the deprecated x-initialSync extension to
initial_sync. Pull request #14281 - Fixed --parallel flag not being honored across all bulk engine calls due to incorrect concurrency limit handling. Pull request #14177
- Removed duplicate publish command registration under alpha after it was promoted to a regular Compose command. Pull request #14272
Why it matters
This release brings improved job support with provider integration, fixes critical bugs in dry-run and service dependencies, and strengthens the provider experience with dedicated networking. Several correctness issues around parallelism and cleanup output are also resolved.
Changelog entry
- Add partial support for manually-triggered jobs (scheduled jobs coming when Docker Engine support lands) Release
- Provider services now participate in image phase with on-demand image distribution Pull request #14252
- Provider relay links get dedicated bridge networks per service Pull request #14275
- Fix --dry-run hanging with
depends_on: condition:service_completed_successfullyPull request #14270 - Pre_start hook containers are now reconciliation plan resources Pull request #14221
- Fix docker compose down --rmi printing misleading dangling image messages Pull request #14266
- Fix --parallel flag not being honored across bulk engine calls Pull request #14177
- Adapt to compose-go v2.16.1 silent x-initialSync promotion Pull request #14281
- Remove duplicate publish command registration under alpha Pull request #14272
Docker Compose v5.6.0 is out. Partial job support for manually-triggered jobs, improved provider integration with image distribution, dedicated networks for provider relays, and fixes for --dry-run and --parallel.
Docker Compose v5.6.0 is available. This release adds partial support for manually-triggered jobs, improves provider-backed services with dedicated bridge networks and image phase participation, and fixes several issues including --dry-run hangs with service dependencies and --parallel flag handling across bulk operations.
Week of September 21, 2026
What shipped
- Provider migration now works correctly — migrating a deployed service to a provider replaces old containers instead of failing on name conflicts. Pull request #14264
- Providers can now query where to bind their relay endpoint so it reaches them on every platform without exposing ports on the LAN. Pull request #14258
- The plan engine now describes the start phase of applications, extending its vocabulary beyond just creation. Pull request #14200
- Service config-hash byte layout is pinned to prevent compose-go struct refactorings from invalidating existing container stamps. Pull request #14215
- Fixed races in restart re-attach anchoring, shutdown log draining, and wait behavior that were causing flaky tests. Pull request #14140
- Fixed --project-directory being ignored when working with OCI artifacts, now correctly resolving relative volume paths. Pull request #14234
- Services reachable only through another service's build.additional_contexts now build correctly even when their own profile is inactive. Pull request #14242
- Fixed e2e test assertions for pull failures to handle daemon-backend dependent error messages and stderr output. Pull request #14245
Why it matters
Provider migration support and relay binding enable better multi-platform deployments. The plan engine improvements and hash pinning strengthen internal architecture while fixes to restart behavior and profile handling address real user issues.
Changelog entry
- Fix provider migration to replace stale service replicas instead of failing on container name conflicts Pull request #14264
- Add get-relay-info command so providers can query where to bind published endpoints Pull request #14258
- Extend plan engine to describe the start phase of applications Pull request #14200
- Pin service config-hash byte layout to prevent compose-go struct refactorings from invalidating container stamps Pull request #14215
- Fix restart re-attach anchor, shutdown log draining, and wait behavior races Pull request #14140
- Fix --project-directory being ignored when using OCI artifacts Pull request #14234
- Fix services in build.additional_contexts to build when referenced service profile is inactive Pull request #14242
- Adopt compose-go jobs and container-spec layering with
pre_starthooks Pull request #14093
This week: provider migration works, relays bind intelligently, plan engine handles start phases, and config hashes stay stable across refactors. Plus fixes for restart races and profile handling.
This week in docker/compose: provider migration now works seamlessly without name conflicts. Providers can query relay binding locations for cross-platform compatibility. The plan engine extends to describe application start phases. Config-hash layout is pinned to prevent future invalidation. Multiple fixes address restart re-attach races, OCI project directories, and service profile handling.