Why are turbo commands echoing its version in stderr?

[joelstransky]

Summary

We have CI on Azure Devops that calls & npx turbo run build --no-daemon which has been fine until recently.
Now it's emitting the turbo version as a stderr ##[error]turbo 2.3.3 which halts the build.
What could possibly be causing this?

Additional information

Locally, the update banner is included and we do not get the stderr of the current version.

╭──────────────────────────────────────────────────────────────────────────╮
│                                                                          │
│                     Update available v2.3.3 ≫ v2.3.4                     │
│    Changelog: https://github.com/vercel/turborepo/releases/tag/v2.3.4    │
│             Run "npx @turbo/codemod@latest update" to update             │
│                                                                          │
│          Follow @turborepo for updates: https://x.com/turborepo          │
╰──────────────────────────────────────────────────────────────────────────╯
turbo 2.3.3

### Example

_No response_

[anthonyshew]

Answered you on Twitter! 😄 Notable that this isn't a new output on our end though, so maybe something changed in Azure Devops. Here's the release that included #8841: https://github.com/vercel/turborepo/releases/tag/v2.0.10-canary.2