• Guard the NATS RPC server against malformed (nil Msg) requests: a bad or empty message is now dropped and logged (subject, sender metadata, reply inbox, payload hex) instead of triggering a nil-pointer panic that crashed the server (#502)
• Bump nats.go to v1.52.0 — this raises the minimum Go version to 1.25 (#502)
• Instrument handler/RPC channel buffers and worker pools with new capacity/utilization metrics (#500)

Hardening + observability patch for the NATS RPC path: fixes a crash when a server receives a malformed/empty request on its RPC subject, refreshes the NATS client to the latest release, and adds buffer/worker-pool metrics on the hot path. Note the minimum Go version is now 1.25.

What's Changed

• fix(agent): capture error code before packetEncodeMessage mutates payload by @victordomiciano in #494

Full Changelog: v2.11.21...v2.11.22

What's Changed

• Add missing viper config for etcd user/pass by @rsafonseca in #469
• [v2] Add IsReady method to App interface and implement connection checks by @ffelipelimao in #475

Full Changelog: 2.11.20...v2.11.21

What's Changed

• fix(metrics): ReportHistogram impl for stasd by @hspedro in #464

Full Changelog: v2.11.18...v2.11.19

What's Changed

• fix(etcd): handle revision errors in watcher by @hspedro in #460

Full Changelog: v2.11.17...v2.11.18

What's Changed

• fix(etcd): reduce log level of sync servers by @hspedro in #459

Full Changelog: v2.11.16...v2.11.17

What's Changed

• refactor(xk6-pitaya): migrate to sobek by @hspedro in #456

Full Changelog: v2.11.15...v2.11.16

What's Changed

• fix(agent): wrap kick error instead of metadata by @hspedro in #455

Full Changelog: v2.11.14...v2.11.15

What's Changed

• Fix some unique session kick failures preventing clients from binding new sessions by @felippeduran in #452

feat(session): propagate network errors on Kick

Kick might fail due to encoding and various network errors during write. Also, if Kick tries to write to a closed connection (fd) it would do so without a timeout, defaulting to the OS timeouts in the order of minutes. New Kick behavior does:

• Uses writeConnection that sets write deadlines
• Propagate encode errors so the client can decide to retry
• Propagate network errors so the client can decide to ignore

Knowing the error is especially useful in the unique_session module, which we need to ensure the existing session is always closed, regardless of a successful Kick.

Full Changelog: v2.11.13...v2.11.14

What's Changed

• Fix dieChan not getting closed or pitaya not terminating on fatal etcd and nats failures by @felippeduran in #447

Full Changelog: v2.11.12...v2.11.13