What Docker Engine changed, 13 April 2026 to 28 September 2026
107 operations became 108. None were removed, 0 were newly deprecated, 1 were added, and 3 request fields became required.
Read from moby/moby at c4f4eb3 and dc0ad36 (version 1.57). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Docker Engine's published specification.
The Docker Engine API is described, in Swagger 2.0 form, in moby/moby, the open-source project Docker Engine is built from. This page reads api/swagger.yaml on the main development branch, which runs ahead of the latest release; the Engine API is versioned by URL path, so check a change against the API version your client negotiates. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (0)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
No operation is currently marked deprecated.
Request fields removed from the specification
The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Docker Engine rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Docker Engine versions — see the note at the top of this page.
- POST /services/{id}/update no longer lists TaskTemplate.ContainerSpec.HealthCheck (application/json)
- POST /services/create no longer lists TaskTemplate.ContainerSpec.HealthCheck (application/json)
Request fields that became required
Only JSON request bodies are compared. A top-level field applies whenever the operation is sent a JSON body. A nested field applies only inside each object containing it that is sent (for an array, each element), so a caller that never sends that object, or sends an empty array, is not affected.
- POST /swarm/join — now requires JoinToken
- POST /swarm/join — now requires ListenAddr
- POST /swarm/join — now requires RemoteAddrs
Docker Engine API questions
Every answer below is computed from the snapshot above, and each links to the Docker Engine specification it was read from.
- Which Docker Engine API endpoints were removed recently?
- None between 13 April 2026 and 28 September 2026, in api/swagger.yaml in moby/moby. It went from 107 to 108 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: moby/moby, the two commits compared
- Which Docker Engine API endpoints are deprecated?
- No operation in api/swagger.yaml in moby/moby, as of 28 September 2026, carries the deprecated flag. A specification can only show a deprecation the vendor marks in it, so Docker Engine's own changelog may still announce one.
- Source: moby/moby, the two commits compared
- Did any Docker Engine API request fields become required?
- 3 JSON request fields became required between 13 April 2026 and 28 September 2026: JoinToken on POST /swarm/join, ListenAddr on POST /swarm/join and RemoteAddrs on POST /swarm/join. They are top-level fields of the JSON request body, so they apply whenever a JSON body is sent: a JSON body that leaves one out no longer matches the current specification.
- Source: moby/moby, the two commits compared
- Where is the Docker Engine OpenAPI specification?
- In the moby/moby repository on GitHub. This page reads api/swagger.yaml at commit dc0ad36 (version 1.57), dated 28 September 2026.
- Source: moby/moby on GitHub
The Action does not check Docker Engine yet
It checks GitHub REST and Stripe. If you want your CI to check the Docker Engine endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.