Simon Ser a96c305b25 build: write --print output to stdout ... stdinfo should only be used for status/progress messages: it defaults to stderr and makes piping the output trickier. bakex always writes `docker buildx bake --print` always uses stdout. Signed-off-by: Simon Ser <contact@emersion.fr>		2025-04-22 10:13:07 +02:00
..
api	introduce build --print to dump equivalent bakefile	2025-03-26 12:24:31 +01:00
compose	build: write --print output to stdout	2025-04-22 10:13:07 +02:00
e2e	introduce volume.type=image	2025-04-09 16:59:42 +02:00
mocks	make the mocks generator happy	2025-02-21 15:23:25 +01:00
progress	can't render progress concurrently with buildkit	2025-01-08 16:12:54 +01:00
prompt	add warning message when a remote configuration include an another remote config	2025-03-07 16:30:32 +01:00
remote	capture git fetch output when debug output is enabled	2025-04-08 12:03:41 +02:00
utils	format code with gofumpt	2024-12-17 16:50:14 +01:00
watch	chore: make function comment match function name	2025-04-16 13:33:16 +02:00