Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
depot-cli v2.102 changed how --file merging works for depot bake: previously a compose override file completely replaced the x-bake tags array, but after the upgrade, tags from both files were merged, so --push tried to push all tags instead of just the override's tag. The change came from the compose-go library upgrade (v2.1.3 to v2.14.0), which switched x-* extensions from replace to standard Compose merge rules (arrays append).
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Use a native Bake target for generated overrides instead of compose override files: {"target": {"static": {"tags": [...]}}} replaces the tags cleanly. The reporter verified both suggested alternatives work. The compose-go merge behavior is the upstream Compose standard, so the native target form is the durable fix.
Source: https://github.com/depot/cli/issues/553
Source: https://github.com/depot/cli/issues/553
Fixes depot-cli v2.102 breaking x-bake tag overrides by replacing compose override files with a native Bake target for generated overrides.
Guide merge-python-client stuck on pydantic v1 breaks v2 codebases; upgrade to the v2 release: Merge resolved this by shipping the SDK on pydantic 2.0 (collaborator dsinghvi confirmed the migration was done).
Fixes a helpdesk agent that cannot parse GlobalProtect logs after a client update changed the format: version-tagged parsers and graceful fallback.