Update Rust crate docker-compose-types to 0.22.0

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Type	Update	Change
docker-compose-types	dependencies	minor	0.7.0 -> 0.22.0

---

Release Notes

stephanbuys/docker-compose-types (docker-compose-types)

v0.22.0

• Restore support for Compose files that use the canonical includes key by
  keeping the field optional and accepting both spellings
• Add regression test coverage for include entries that provide a list of paths

v0.21.0

(Thanks to @​hamnis)

• Derive Default for Healthcheck (#​60)
• Add dns_opt to Service (#​61)

v0.20.0

(Thanks to @​hamnnis)

• Add restart and required to DependsCondition (#​55)
• Allow Include.path to be a string or a list (#​56)
• Add serde_norway as an alternative YAML backend (#​58)

(Thanks to @​glueball)

• Add support for dockerfile_inline in Advanced build step (#​57)

(Thanks to @​ava57r)

• Add skip_serializing_if for Resources (#​59)

v0.19.0

(Thanks to @​hamnnis)

• Add includes to compose file

v0.18.0

(Thanks to @​John-Vash)

• Add runtime field to Service as per https://docs.docker.com/compose/compose-file/compose-file-v3/#runtime

v0.17.0

(Thanks to @​lambdaclass)

• Add subpath option for advanced volumes

v0.16.0

(Thanks to @​snaggen)

Make Compose compatible with output from "docker compose config"

• Updated Volume bind filed
  • Made propagation optional, and added additional fields to comply
    with https://docs.docker.com/reference/compose-file/services/#volumes
• Allow toplevel field 'name'
  • ref. https://docs.docker.com/reference/compose-file/version-and-name/
• Handle empty volume fields
  • Make Volume nocopy optional

v0.15.0

(Thanks to @​snaggen)

• Add the start_interval field to Healthcheck as
  per https://docs.docker.com/reference/compose-file/services/#healthcheck

v0.14.0

(Thanks to @​Ptrskay3)

• Add mem_limit, mem_reservation and mem_swappiness based
  on https://docs.docker.com/reference/compose-file/services/#mem_limit

(Other)

• Fix indexmap feature issue when not using default features of the crate.

v0.13.0

(Thanks to @​snaggen)

• Support for devices in reservations https://docs.docker.com/compose/compose-file/deploy/#devices

(Thanks to @​pbrant)

• Support for domainname in Service https://docs.docker.com/compose/compose-file/05-services/#domainname

v0.12.0

(Thanks to @​snaggen)

• Support for read_only images https://docs.docker.com/compose/compose-file/05-services/

v0.11.0

(Thanks to @​snaggen)

• Add support for gid (numerical) groups

v0.10.0

(Thanks to @​snaggen)

• Support the alternative notation for extends in services. As
  per https://docs.docker.com/compose/multiple-compose-files/extends/#extending-services-within-the-same-file

v0.9.0

(Thanks to @​pbrant)

• Add cgroup_parent to Service

v0.8.0

• Bump indexmap to 2.2
• Bump derive_builder to 0.20
• Add serde_yml as alternative to serde_yaml as the latter is no longer maintained
  (Looking for feedback on this, currently behind yml and yaml feature flags, serde_yaml is still the default)

---

Configuration

📅 Schedule: 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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.22.0
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)