Skip to content

Tested versions

The adapter's tests run against an embedded NATS server, in process. They do not start a server container, and no tests run against a server of any other version.

Component Version Where it comes from
nats-server v2.15.1 go.mod: an indirect requirement, pulled in by go/nats v0.2.4.
nats.go v1.55.0 go.mod: a direct requirement.
go/nats v0.2.4 go.mod. It builds the embedded server and the client.
go/messaging v0.9.0 go.mod. The conformance suite is this version's.
Go 1.27.3 The go directive in go.mod.

These are the versions on main. A release pins whatever main held when it was cut.

How the server is started

  • Core is tested through natstest.StartServer, one in-process server for each test.
  • JetStream is tested through a fixture that builds a server with JetStream: true and a store directory it owns, over server.New and server.Start. Restart stops the server and starts a new one on the same directory, which is how the durable suite's restart rows run.

Both run through client.InProcess, so no TCP listener is involved.

What this does not tell you

  • A network server. The client and server are in one process and talk over an in-memory connection. TLS, authentication and the connection's behaviour across a real network are not exercised.
  • A cluster. The fixtures run one server. Replicated streams are not tested.
  • Other server versions. Nothing here establishes a minimum or maximum server version.
  • nats.go versions. The measured limit a consumer deleted just after Subscribe is noticed late was measured on nats.go v1.54.0 and v1.55.0.

The adapter's tests are go test ./.... See Run the conformance suite.