NDEx Java Client version 3.0.2

[3.0.2] - 2026-09-04

Fixed

• A successful CX2 network update was reported as a failure. updateCX2Network treated only 204 No Content as success, but PUT /v3/networks/{networkid} answers 200 with an NdexObjectUpdateStatus body. A successful v3 update therefore took the error path, where its own success body failed to parse as an NDExError and surfaced as Unrecognized field "uuid" — on an update the server had already applied, making it a false failure a caller would retry. Any 2xx is now treated as success, so both the v2 (204) and v3 (200) contracts are honoured.
• Update errors are read from the error stream. The same method read the response body with getInputStream(), which throws for a 4xx or 5xx, so a genuine server error surfaced as an IOException rather than the NdexException the body describes. It now reads getErrorStream(), matching every other method in the client.