Repository navigation
@odatano/nightgate 0.35.0
@odatano/nightgate 0.35.0
Services under /odata/v4/midnight…; the /api/v1/… paths keep answering until 1.0. No schema change, no circuit change.
- Service paths:
/odata/v4/midnight,/odata/v4/midnight-indexer,/odata/v4/midnight-verify,/odata/v4/midnight-analytics,/odata/v4/midnight-admin. Names, model and handlers unchanged;/contract-manifestand/zk-config/*stay. - The agent-token lane and the public verify lane sit on the new paths; container healthcheck and watchdog read
/odata/v4/midnight-indexer/getReadiness(). /api/v1/nightgate,/api/v1/indexer,/api/v1/verify,/api/v1/analytics,/api/v1/adminare rewritten to the new paths, logged once per path and counted ingetMetrics()aslegacy_path_requests_total{path}. They go with 1.0.@odatano/nightgate-tx0.14.0:connect()defaultsservicePathto/odata/v4/midnightandindexerServicePath(getHealth()) to/odata/v4/midnight-indexer; against a server below 0.35.0 pass the/api/v1/…paths.
Full Changelog: v0.34.0...v0.35.0