Repository navigation
latest moves from 4.2.1 to 4.2.2: a warning when anyone on the network can use the gateway, and plain debug logs with NO_COLOR. No new options, and nothing changes for clients.
Changes
- A warning when anyone on the network can use the gateway. A gateway serving MCP without an API key on an address other machines can reach (no
--host,0.0.0.0,::or a network address) prints oneWARNING: No API key is setline on stderr after its startup listing, even with--logLevel none. With several servers in a--configfile, it names the ones without a key.--apiKey,SUPERGATEWAY_API_KEYor--host 127.0.0.1turn it off. It changes nothing else (#360, #370, #371) - Debug logs honour
NO_COLOR. With--logLevel debugin a terminal,NO_COLOR,FORCE_COLOR=0andTERM=dumbnow turn colour off (#368)
Validation
New tests cover the warning on every output, wildcard, network and loopback address, every way to set a key, --logLevel none, JSON logs and config files with one or several servers, and check that clients without a key are still served. 4.2.2-rc.1 passed a 25-hour soak on Linux, Windows and macOS.
Thanks to: