Skip to content

remove API-version compatibility for API < v1.44 - #6551

Merged
thaJeztah merged 5 commits into
docker:masterfrom
thaJeztah:remove_legacy_api_versions
Oct 10, 2025
Merged

remove API-version compatibility for API < v1.44#6551
thaJeztah merged 5 commits into
docker:masterfrom
thaJeztah:remove_legacy_api_versions

Conversation

@thaJeztah

@thaJeztahthaJeztah commented Oct 10, 2025

Copy link
Copy Markdown
Member

relates to:

remove API-version compatibility for API < v1.44

Support for API versions < v1.44 was removed in the client in moby@96b29f5
and moby@7652f38, so we can remove fallback-code from the CLI as well,
as it won't be able to use those versions.

cli/command/container: rm use of deprecated MacAddress field

This field is no longer in use since API v1.44.

cli/command/service: remove AppendServiceStatus (API <v1.41)

This function was added in 7405ac5 as
a fallback for API < v1.41, which did not include the service status
in the response. Current API versions return this information, so there's
no need to fetch it manually.

It was not gated by API version for some tests (which didn't set API
version), but should not be needed for non-test situations.

cli/command/container, image: remove addPlatformFlag utility

It was created for api-version conditionally setting the flag options.

docs: update some versions in examples

- Human readable description for the release notes

remove API-version compatibility for API < v1.44 (docker 24.0 and older)

- A picture of a cute animal (not mandatory but encouraged)

@thaJeztahthaJeztah added this to the 29.0.0 milestone Oct 10, 2025
@thaJeztahthaJeztah changed the title Remove legacy api versionsremove API-version compatibility for API < v1.44Oct 10, 2025
@codecov-commenter

codecov-commenter commented Oct 10, 2025

Copy link
Copy Markdown

@thaJeztah
thaJeztahforce-pushed the remove_legacy_api_versions branch 2 times, most recently from 6d4b033 to 8f7cc42CompareOctober 10, 2025 17:47
@thaJeztah
thaJeztah marked this pull request as ready for review October 10, 2025 17:48
@thaJeztah
thaJeztah requested review from a team and silvin-lubecki as code ownersOctober 10, 2025 17:48
@thaJeztah
thaJeztahforce-pushed the remove_legacy_api_versions branch 3 times, most recently from 1ce0591 to c939c9bCompareOctober 10, 2025 19:20
Support for API versions < v1.44 was removed in the client in [moby@96b29f5]
and [moby@7652f38], so we can remove fallback-code from the CLI as well,
as it won't be able to use those versions.
[moby@96b29f5]: moby/moby@96b29f5
[moby@7652f38]: moby/moby@7652f38
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This field is no longer in use since API v1.44.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This function was added in 7405ac5 as
a fallback for API < v1.41, which did not include the service status
in the response. Current API versions return this information, so there's
no need to fetch it manually.
It was not gated by API version for some tests (which didn't set API
version), but should not be needed for non-test situations.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah
thaJeztahforce-pushed the remove_legacy_api_versions branch from c939c9b to 5ad9145CompareOctober 10, 2025 19:28
@thaJeztah

Copy link
Copy Markdown
MemberAuthor

thanks!

@thaJeztah
thaJeztah merged commit 01febbc into docker:masterOct 10, 2025
97 of 99 checks passed
@thaJeztah
thaJeztah deleted the remove_legacy_api_versions branch October 10, 2025 20:53
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@thaJeztah@codecov-commenter@robmry