Skip to content

api/types/system: remove deprecated Commit.Expected field#51127

Merged
akerouanton merged 1 commit intomoby:masterfrom
thaJeztah:info_remove_deprecated
Oct 8, 2025
Merged

api/types/system: remove deprecated Commit.Expected field#51127
akerouanton merged 1 commit intomoby:masterfrom
thaJeztah:info_remove_deprecated

Conversation

@thaJeztah
Copy link
Member

relates to:

api/types/system: remove deprecated Commit.Expected field

This field was deprecated API v1.48 in moby@ff191c5, and removed in API v1.49 in moby@564abf9.

This patch:

  • Removes the field from the API Go types.
  • Reimplements the /info endpoint with the compat package to replace the local infoResponse implementation.
  • Removes the ServiceConfig.ExtraFields field in api/types/registry introduced in moby@7d9c50d to backfill the AllowNondistributableArtifactsCIDRs and AllowNondistributableArtifactsHostnames fields for API < v1.47.

We should also consider deprecating the ContainerdCommit, RuncCommit and InitCommit fields on the /info response (as we also include this information as part of the components returned in /version), but those can still be useful currently for situations where a user only provides docker info output.

- What I did

- How I did it

- How to verify it

- Human readable description for the release notes

GO SDK: api/types/system: remove deprecated `Commit.Expected` field.

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

This field was deprecated API v1.48 in [moby/moby@ff191c5], and removed in
API v1.49 in [moby/moby@564abf9].

This patch:

- Removes the field from the API Go types.
- Reimplements the `/info` endpoint with the `compat` package to replace
  the local `infoResponse` implementation.
- Removes the `ServiceConfig.ExtraFields` field in api/types/registry
  introduced in [moby/moby@7d9c50d] to backfill the `AllowNondistributableArtifactsCIDRs`
  and `AllowNondistributableArtifactsHostnames` fields for API < v1.47.

We should also consider deprecating the `ContainerdCommit`, `RuncCommit`
and `InitCommit` fields on the `/info` response (as we also include this
information as part of the components returned in `/version`), but those
can still be useful currently for situations where a user only provides
`docker info` output.

[moby/moby@ff191c5]: moby@ff191c5
[moby/moby@564abf9]: moby@564abf9
[moby/moby@7d9c50d]: moby@7d9c50d

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah added this to the 29.0.0 milestone Oct 7, 2025
@thaJeztah thaJeztah added area/api API status/2-code-review impact/deprecation impact/go-sdk Noteworthy (compatibility changes) in the Go SDK release-blocker PRs we want to block a release on module/api kind/refactor PR's that refactor, or clean-up code labels Oct 7, 2025
@thaJeztah thaJeztah marked this pull request as ready for review October 7, 2025 17:34
Copy link
Member

@akerouanton akerouanton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@akerouanton akerouanton merged commit 45bc224 into moby:master Oct 8, 2025
227 of 235 checks passed
@thaJeztah thaJeztah deleted the info_remove_deprecated branch October 8, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/api API impact/deprecation impact/go-sdk Noteworthy (compatibility changes) in the Go SDK kind/refactor PR's that refactor, or clean-up code module/api release-blocker PRs we want to block a release on status/2-code-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants