fix(system): probe real /api/v1/version instead of 404ing /system/version #135
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/mapps-151-spa-version-probe-path"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The SPA's version probe pointed at /api/v1/system/version, an endpoint mokosh-server never deployed, so every admin layout mount issued a request that 404'd against the "Not a frontend" fallback. The live build-info endpoint is /api/v1/version (the same one the System Status page already probes), which returns the server's running version but no registry "latest available" poll.
Repoint VERSION_PATH at /version and reshape the response to the real body (ServerVersionResponse { version }, extra build-info fields dropped). Since the endpoint reports only what the server runs, server.latest stays None (its banner line is hidden) and the server's version is treated as the client's "latest": mokosh-server and mokosh-www release together, so a loaded bundle older than the server's version is stale and flags the update banner, fixing the silently-broken compatibility check that left the footer showing 0.1.0 while the backend reported 0.2.0.
#MAPPS-151
The SPA's version probe pointed at /api/v1/system/version, an endpoint mokosh-server never deployed, so every admin layout mount issued a request that 404'd against the "Not a frontend" fallback. The live build-info endpoint is /api/v1/version (the same one the System Status page already probes), which returns the server's running version but no registry "latest available" poll. Repoint VERSION_PATH at /version and reshape the response to the real body (ServerVersionResponse { version }, extra build-info fields dropped). Since the endpoint reports only what the server runs, server.latest stays None (its banner line is hidden) and the server's version is treated as the client's "latest": mokosh-server and mokosh-www release together, so a loaded bundle older than the server's version is stale and flags the update banner, fixing the silently-broken compatibility check that left the footer showing 0.1.0 while the backend reported 0.2.0. #MAPPS-151