3.37.0

gs_gateways_disconnected_total metric, counting gateway disconnections by protocol and by the error the connection was disconnected with. This makes disconnection reasons (such as gateways disappearing without a close handshake, or missing too many pongs) observable as a rate, instead of only through logs.
ttgc.managed-gateway-euis configuration option: Gateway EUI prefixes of managed gateways, defaulting to the EUI prefix of The Things Industries managed gateways. Gateways outside these prefixes are reported as not managed in the claiming info.
ttgc.lbscups.lns-port configuration option: the LoRa Basics Station LNS port of the Gateway Server, defaulting to 8887.
Downlink scheduling on all antennas of a gateway. Previously, only the first antenna could be used as a downlink path, and uplinks received on any other antenna had their downlink path disabled.
events.redis.store.expire-limiter-size configuration option: how many entity event streams the PEXPIRE rate limiter tracks, at 8 bytes each, defaulting to 4194304 (32 MiB). A negative value refreshes the TTL on every event.

In the Semtech UDP Packet Forwarder protocol, PUSH_ACK and PULL_ACK are only sent after the gateway has connected to the Gateway Server and the gateway’s PUSH_DATA or PULL_DATA respectively has been accepted.
Don’t log a Task failed warning in GS for every task attached to a gateway connection when that connection is closed. The tasks that run for the lifetime of a gateway connection now stop without an error when the connection is closed, and the disconnection is logged once, as Disconnected, including the reason. This removes several duplicate warnings per gateway disconnection, which were particularly noisy for gateways on unreliable backhaul.
Websocket close errors on the LoRa Basics Station frontend (such as websocket: close 1006 (abnormal closure): unexpected EOF, which is what a gateway disappearing without a close handshake looks like) are now reported as the defined error pkg/gatewayserver/io/semtechws:websocket_closed, with the close code as an attribute and the original error as the cause. As a result, the gs.gateway.disconnect event for these disconnections now carries structured error details instead of a plain string; consumers that parse the event data should expect the ErrorDetails format.

Federated (OIDC/SSO) login no longer fails with unverified_email for identity providers such as Okta that omit the email_verified claim from the ID token and only provide it via the userinfo endpoint. When the ID token contains an email address but no email_verified claim, the verification status is now retrieved from the userinfo endpoint, provided the userinfo subject and email address match the ID token. An explicit email_verified: false in the ID token is still rejected.
Parsing of the rctx field in the upinfo object of upstream messages received via the LoRa Basics Station LNS protocol. The field name was misspelled as rtcx, so the radio context reported by gateways was ignored. The antenna index in the uplink metadata now reflects the reported radio context and is echoed back in class A downlinks, instead of always being 0.
The antenna gain sent to LoRa Basics Station gateways in the router configuration. Each board’s radio configuration now uses the gain of its own antenna instead of applying the first antenna’s gain to all boards, and fractional gains are no longer truncated.
Memory of event-publishing components (most visibly the Application Server and Network Server) no longer grows with the number of entities. The PEXPIRE rate limiting added in v3.36.2 kept an entry per entity; it now uses a fixed-size table. PEXPIRE load and event history retention are unchanged.