Skip to content

[28.x backport] api/docs: remove BuildCache.Parent field for API v1.42 and up#51396

Merged
vvoland merged 1 commit intomoby:28.xfrom
thaJeztah:28.x_backport_api_docs
Nov 5, 2025
Merged

[28.x backport] api/docs: remove BuildCache.Parent field for API v1.42 and up#51396
vvoland merged 1 commit intomoby:28.xfrom
thaJeztah:28.x_backport_api_docs

Conversation

@thaJeztah
Copy link
Copy Markdown
Member

The BuildCache.Parent field was removed in API v1.42 in moby@e0db820. While we had to keep the Go struct field around to backfil the field for older API versions, it's no longer part of API v1.42 and up (using the "omitempty" is just an implementation detail).

This patch corrects the swagger files to match this.

- What I did

- How I did it

- How to verify it

- Human readable description for the release notes

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

The BuildCache.Parent field was removed in API v1.42 in [moby/moby@e0db820].
While we had to keep the Go struct field around to backfil the field for
older API versions, it's no longer part of API v1.42 and up (using the
"omitempty" is just an implementation detail).

This patch corrects the swagger files to match this.

[moby/moby@e0db820]: moby@e0db820

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit a5d9619)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah added this to the 28.5.2 milestone Nov 5, 2025
@thaJeztah thaJeztah changed the title api/docs: remove BuildCache.Parent field for API v1.42 and up [28.x backport] api/docs: remove BuildCache.Parent field for API v1.42 and up Nov 5, 2025
@thaJeztah thaJeztah marked this pull request as ready for review November 5, 2025 11:09
@vvoland vvoland merged commit 89c5e8f into moby:28.x Nov 5, 2025
61 of 66 checks passed
@thaJeztah thaJeztah deleted the 28.x_backport_api_docs branch November 5, 2025 14:23
Sign up for free to 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