Skip to content

Update dependency docker/compose to v5 - #236

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/docker-compose-5.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/docker-compose-5.x

Conversation

@renovate

@renovate renovate Bot commented Aug 18, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
docker/compose major 2.32.4 → 5.8.0

Release Notes

docker/compose

v5.8.0

Compare Source

What's Changed

ℹ️ Scheduled jobs are now supported. A job is a one-shot unit of work declared in the top-level jobs: element of your Compose file, run on demand or on a schedule.
Scheduling needs Docker Engine 29.10 or later with the jobs extension enabled (it is off by default: dockerd --extension-enable org.mobyproject.jobs.v0). Manual jobs keep working on any engine, and projects that declare no jobs are unaffected.

services:
  db:
    image: postgres
jobs:
  backup:
    image: backup-tool
    depends_on: [db]
    triggers:
      schedule:
        - cron: "0 3 * * *"
  • docker compose up (or create) registers the scheduled jobs with the engine, which fires them on its own clock; docker compose down removes them. On an engine without jobs support, up refuses a project with scheduled jobs before creating anything.
  • docker compose run backup triggers a job right away: its dependencies start first, its logs are streamed and its exit code is returned. On an engine without jobs support, it runs as a one-off service with a warning, as before.
✨ Improvements

Jobs

Full Changelog: docker/compose@v5.7.2...v5.8.0

v5.7.2

Compare Source

What's Changed

✨ Improvements
🐛 Fixes
🔧 Internal
⚙️ Dependencies

New Contributors

Full Changelog: docker/compose@v5.7.1...v5.7.2

v5.7.1

Compare Source

What's Changed
Fixes 🐛
  • fix(oci): verify the manifests fetched against their digest, and take only complete cache entries by @​ndeloof in #​14490
  • fix(oci): keep the cache of extracted projects consistent on interruption and concurrent access by @​ndeloof in #​14462
  • fix(git): check a commit out aside, and keep the cache of remote resources in a directory for each kind by @​ndeloof in #​14475
  • fix(compose): report network and volume progress once, on their own row by @​glours in #​14467
  • fix(config): warn about ignored uid/gid/mode at creation, not at load by @​ndeloof in #​14299
  • fix(down): preserve images outside selected services by @​Aghayenoor in #​14458
  • fix(events): treat io.EOF as a normal end of a bounded stream by @​Bruce848647703 in #​14444
Internal 🔧
Bumps
New Contributors

Full Changelog: docker/compose@v5.7.0...v5.7.1

v5.7.0

Compare Source

What's Changed

ℹ️ Heads-up 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 (#​14290) and interactive up (#​14305), as scale, watch rebuilds and start already do (#​14291, #​14296). The CLI behaves as before. If you call api.Compose.Up from your own program:

  • Up now validates its options first, with the same rules as the CLI flags: UpOptions.Validate() returns an *api.IncompatibleOptionsError (errors.Is(err, api.ErrIncompatibleOptions)) for Start.Wait combined with Start.Attach, and for a detached Up (no Start.Attach) combined with OnExit, ExitCodeFrom or Watch. Those combinations used to be silently ignored (#​14306).
  • Up works on the project it is given and ignores StartOptions.Project.
  • The daemon is not observed again between the two phases: a container that exits after the plan is built is not started again, and one removed in between makes its start fail instead of being skipped. A planning error of the Start phase now fails before any container is created.
  • A foreground Up now gives a use_api_socket service its /run/secrets/docker/config.json, as up -d does, and shows the output of pre_start hooks.
  • The keyboard menu of an interactive up is no longer built by the library: set NavigationMenu: true and pass an implementation with compose.WithNavigationMenu(...), otherwise no menu is displayed and a warning says so (#​14324).

Other changes to the library surface in this release: DownOptions.Images is now an api.ImagePruneMode (untyped constants still compile, a string variable needs a conversion) and an invalid value is rejected before Down removes anything (#​14149); compose.ServiceHash, compose.NetworkHash and compose.VolumeHash are no longer exported, the helpers having moved to an internal package (#​14405); api.Compose is now assembled from six smaller interfaces, with the same method set (#​14322); PushOptions.IgnoreMissing is added.

✨ Improvements

Execution plan

Commands

Other

🐛 Fixes
🔧 Internal
⚙️ Dependencies
New Contributors

Full Changelog: docker/compose@v5.6.1...v5.7.0

v5.6.1

Compare Source

update to go1.26.10
These releases include 1 security fix following the security policy:

  • crypto/x509: mitigation for security concerns with a specific Certificate Authority

    We're blocking trust in a small set of intermediate certificates due to specific security concerns around their operation.

    Verify will now filter out chains which contain these intermediates, preventing them from being returned to the caller.

    We highly recommend immediately upgrading to this release.

    This is CVE-2026-111943 and Go issue https://go.dev/issue/82345.

Full Changelog: docker/compose@v5.6.0...v5.6.1

v5.6.0

Compare Source

What's Changed

ℹ️ This release adds partial support for jobs: only manually-triggered jobs are supported for now, scheduled jobs are not yet available. Full job support will land once the corresponding Docker Engine support is merged.

✨ Improvements

Jobs

Provider services

Other

🐛 Fixes
🔧 Internal
⚙️ Dependencies

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from 9a1b41c to b8bc1d6 Compare September 3, 2026 23:44
@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from b8bc1d6 to 3e5d843 Compare October 2, 2026 16:36
@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from 3e5d843 to 443205f Compare October 21, 2026 11:39
@renovate renovate Bot changed the title chore(deps): update dependency docker/compose to v5 Update dependency docker/compose to v5 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from 443205f to 128e097 Compare November 2, 2026 18:48
@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from 128e097 to 0c026d9 Compare November 11, 2026 10:31
@renovate
renovate Bot force-pushed the renovate/docker-compose-5.x branch from 0c026d9 to c3930b7 Compare November 17, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants