Shipped · DevOps and infrastructure

What docker/compose shipped

The public repository of Docker · github.com/docker/compose

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

Or Use it as a GitHub Action

See the update FoxPlug writes for compose, free

Week of November 9, 2026

What shipped

Why it matters

This week brings a v5.7.1 release and a set of fixes around volumes, scaling and OCI and Git caching that affect how projects are pulled and torn down. Users of down -v with a service selection should see fewer surprises with shared volumes, and the cache fixes make interrupted pulls and concurrent access less likely to leave inconsistent state.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Compose v5.7.1 is out. down -v with services no longer removes volumes other services use, --scale rejects empty service names, and OCI manifests are verified against their digest. Plus a split cache for Git and OCI resources and an update to Go 1.27.4.

Post for LinkedIn

Compose v5.7.1 is out this week. It brings OCI manifest verification against the requested digest, cache handling that stays consistent on interruption and concurrent access, and a Git checkout that is kept only once complete. docker compose down -v with a service selection no longer removes volumes used by services outside that selection, and the --scale flag now rejects an empty service name. compose config --images skips provider services that declare neither an image nor a build. Remote resource caches now have a directory per kind. The project was updated to Go 1.27.4 with its security fixes.

Week of November 2, 2026

What shipped

Why it matters

This week brought v5.7.0, which changes how up runs its Create and Start phases as a single plan while keeping the CLI the same, and notes this matters to people using Compose as a library. It also fixed several user-facing problems: duplicated network and volume progress, images outside the teardown selection being removed by down --rmi, OCI project cache consistency under interruption and concurrent access, and events --until ending with an EOF error.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Compose v5.7.0 is out. up now runs Create and Start as one plan over one daemon snapshot for up -d and interactive up; CLI unchanged. Also fixed: duplicate network/volume progress, down --rmi removing images of unselected services, OCI cache consistency, and events --until EOF ha

Post for LinkedIn

Compose v5.7.0 is out. For users of Compose as a library, up now runs its Create and Start phases as a single plan over a single daemon snapshot, for up -d and interactive up, as scale, watch rebuilds and start already do. The CLI behaves as before. This week also fixed duplicate network and volume progress in up, create and run; down --rmi local|all removing images of services outside the teardown selection; the extracted OCI project cache staying consistent on interruption and concurrent access; and events --until treating the end of a bounded stream as an error. Smaller changes moved images, logs and attach into their own internal packages without behavior changes and migrated more end-to-end tests to the Scenario DSL.

Week of October 26, 2026

What shipped

Why it matters

This week's changes fix several things users hit in day-to-day use: the timeout flag on an attached up, slow dependency checks, volumes removed by down -v that the project does not own, and bake builds ignoring the parallel limit. Much of the remaining work moves code out of the flat pkg/compose package into internal packages and prepares the foreground up to run on the plan engine, with new end-to-end tests pinning its behavior.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week in Compose: attached up now honors -t when it stops the app, depends_on health checks skip the first 500ms wait when already satisfied, down -v keeps volumes the project does not own, --parallel reaches bake as --jobs, and watch handles bind paths starting with two dots

Post for LinkedIn

This week in Compose brings several fixes for common workflows. An attached up that stops the application itself now honors the -t/--timeout flag instead of waiting for each service's stop_grace_period. depends_on conditions are checked before the first poll tick, so an already healthy dependency no longer costs an extra wait. down -v now keeps named volumes the project does not own, and warns instead. The --parallel limit and COMPOSE_PARALLEL_LIMIT are passed to bake as --jobs so builds respect the limit again. compose watch recognizes bind-mounted paths starting with two dots, and compose start gives a use_api_socket service its config file. Alongside these, refactoring continues to split pkg/compose into internal packages, and the foreground up gains end-to-end tests ahead of its move t

Week of October 19, 2026

What shipped

Why it matters

This week brings a security update plus two fixes that affect everyday use:.git changes no longer reach containers under watch, and run now preserves a recreated dependency's anonymous volumes. Compose files also gain the umask service attribute for engines that support it.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Compose v5.6.1 is out with go1.26.10 and a crypto/x509 security fix. Also this week: watch ignores.git at any depth, run keeps a recreated dependency's anonymous volumes, and the umask service attribute is supported.

Post for LinkedIn

Compose v5.6.1 is released, updating to go1.26.10 and including one crypto/x509 security fix that blocks trust in a small set of intermediate certificates. This week also brings two fixes for common workflows. docker compose watch now ignores.git at any depth inside the watched path, so git operations are no longer synced into containers and edits no longer trigger rebuilds that never stop. docker compose run now keeps the anonymous volumes of a recreated dependency whose configuration changed, matching up, so a database dependency no longer looks wiped. Compose files can also set a service container's umask with the umask attribute, with a clear error on engines that would ignore it.

Week of October 12, 2026

What shipped

Why it matters

This week brings two new opt-in flags to stats and a safer push option for images missing locally, plus a way for run to keep existing dependency state. Several fixes target builds and hooks: dry-run no longer executes providers or models, builds keep their failure reason and permissions, and pre_start hooks get their env_file variables.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week in docker/compose: push got --ignore-missing and --ignore-push-failures is deprecated, stats added --all-projects and --aggregate, and run gained --no-recreate. Also fixes for build errors being dropped, bake permissions, dry-run executing providers, and pre_start hook

Post for LinkedIn

This week in docker/compose: push has a new --ignore-missing flag that skips images not available locally, and --ignore-push-failures is now deprecated in its favor. docker compose stats added opt-in --all-projects and --aggregate flags. docker compose run gained --no-recreate to reuse existing dependencies as-is. On the fix side: build now reads bake's stderr to the end so failure reasons are not dropped, missing entitlement grants with recent Buildx are handled, dry-run no longer executes providers or models, pre_start hooks receive their env_file variables, and watch skips sync+exec triggers on bind-mounted paths. Services can also opt out of their name as a network alias with use_service_name_alias.

Week of October 5, 2026

What shipped

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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

Post for LinkedIn

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

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-16.

Is this your repo? Ask us to remove this page.

Leaderboard