Skip to content

Commit 54e2ce3

Browse files
docs(observability): rewrap release channel paragraph
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 0959cda commit 54e2ce3

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/operations/observability.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -629,8 +629,8 @@ resource attributes, such as `OTEL_RESOURCE_ATTRIBUTES=deployment.environment.na
629629

630630
Each process reports its own build, not the one it talks to: the server, the desktop main process,
631631
the UI, and the mobile app each carry `t3code.release.channel` (`dev`, `stable`, `nightly`, or
632-
`preview`, from their own version; desktop PR builds count as `preview`) and `deployment.environment.name` (`development`, `production`,
633-
or `staging` for `preview`). On the server and the desktop main process either key in
632+
`preview`, from their own version; desktop PR builds count as `preview`) and
633+
`deployment.environment.name` (`development`, `production`, or `staging` for `preview`). On the server and the desktop main process either key in
634634
`OTEL_RESOURCE_ATTRIBUTES` wins. The UI and mobile app never read that variable: Vercel PR previews
635635
set `VITE_RELEASE_CHANNEL=preview` because their `APP_VERSION` must stay comparable with the
636636
server's, and the mobile app maps its build variant (`development`, `preview`, `production`).

0 commit comments

Comments
 (0)