imbajin opened a new issue, #319: URL: https://github.com/apache/hugegraph-ai/issues/319
## Background The current python-client CI workflow still starts `hugegraph/hugegraph:1.3.0` in [`.github/workflows/hugegraph-python-client.yml`](https://github.com/apache/hugegraph-ai/blob/main/.github/workflows/hugegraph-python-client.yml). The file already carries a TODO for upgrading the server version, and PR #318 had to add a compatibility gate around `/metrics/system` because the legacy server returns 500 there. ## Task Upgrade the HugeGraph server used by python-client CI to `1.7`, then adapt the client tests and compatibility assumptions to the newer server behavior. ## Scope - Update the workflow image tag from `1.3.0` to `1.7.x` in `.github/workflows/hugegraph-python-client.yml`. - Revisit python-client integration tests that currently encode old-server behavior. - Remove temporary compatibility gates once CI runs against the newer server version. - Verify the latest client code paths against HugeGraph 1.7 responses and error handling. ## Acceptance Criteria - python-client CI runs against HugeGraph 1.7 successfully. - tests reflect current server behavior instead of legacy 1.3.0 quirks. - any required client-side adjustments for 1.7 are included and documented in the PR. ## Notes - Recent context: PR #318 (`refactor: remove 'incubating' branding, update docs & packaging`) exposed that the workflow is still pinned to an old server image.\n- If 1.7 introduces API or payload differences, please update the relevant tests first and then tighten the assertions around the new behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
