Breaking API Change for changelog:

The presence of theip field oncodersdk.ConnectionLog cannot be guaranteed, and so the field has been made optional. It may be omitted on API responses.

When running a scaletest, I noticed logs of the form:

2025-09-12 06:34:10.924 [erro]  coderd.workspaceapps: upsert connection log failed  trace=0xa17580  span=0xa17620  workspace_id=81b937d7-5777-4df5-b5cb-80241f30326f  agent_id=78b2ff6d-b4a6-4a4e-88a7-283e05455a88  app_id=00000000-0000-0000-0000-000000000000  user_id=00000000-0000-0000-0000-000000000000  user_agent=""  app_slug_or_port=terminal  status_code=404  request_id=67f03cf8-9523-444a-97bc-90de080a54c8 ...    error= 1 error occurred:           * pq: null value in column "ip" of relation "connection_logs" violates not-null constraint

to ensure logs are never omitted from the connection log due to a missing IP again (i.e. I'm not sure if we can always rely on a valid, parseable, IP from(http.Request).RemoteAddr), I've removed theNOT NULL constraint onip onconnection_logs, and madeip on the API response optional.

The specific cause for these null IPs was the/workspaceproxies/me/issue-signed-app-token [post] endpoint constructing it's ownhttp.Request without aRemoteAddr set, and then passing that to the token issuer.

To solve this, we'll have workspace proxies send the real IP of the client when calling/workspaceproxies/me/issue-signed-app-token [post] via the headerCoder-Workspace-Proxy-Real-IP.