fix: error/info messages not printed with --output-json

[rocketeerbkw]

General Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

When using --output-json and the lagoon-cli attempts to render an Error or Info, the output is empty and errors are lost. This fixes RenderError and RenderInfo to print when --output-json flag is passed.

Note: There are some commands that will return BOTH Error and Info, or an Info and other output, which means it technically outputs invalid JSON, but I think that's better than now printing errors at all.

Closing issues

n/a

[shreddedbacon]

Note: There are some commands that will return BOTH Error and Info, or an Info and other output, which means it technically outputs invalid JSON, but I think that's better than now printing errors at all.

Do you know which ones? I'd like to do sidebyside check for some of these

[rocketeerbkw]

Just search for all uses of ‘RenderInfo’, it should be obvious. Off the top of my head, the update check and ssh key parsing call it and continue execution which means another renderer can be called later. — Thanks, Brandon

…

On Mon, Jan 26, 2026 at 10:51 PM Ben Jackson ***@***.***> wrote: *shreddedbacon* left a comment (uselagoon/lagoon-cli#486) <#486 (comment)> Note: There are some commands that will return BOTH Error and Info, or an Info and other output, which means it technically outputs invalid JSON, but I think that's better than now printing errors at all. Do you know which ones? I'd like to do sidebyside check for some of these — Reply to this email directly, view it on GitHub <#486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWSUZL2JNVNAGOBI2TC6L4I3VGNAVCNFSM6AAAAACS7UEE7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBTGEYDKNJXGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>