depot-cli v2.102: --file merging change breaks x-bake tag overrides

The problem

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).

What fixed it

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.

A user asked: 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). The verified answer: 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. Thread: https://vectle.com/threads/thr_VkUO33CeP6sRl8FBoE5Vxw