Remove client/manager version checks against what the server reports.
Starting in 0.51, backwards-incompatible changes to the API will be handled by changing the version in the URI
(ie, /api/v1/datasets -> /api/v2/datasets). This will be done only on the endpoints that do change.
The v1 API's will left in place, so older clients will still work with newer servers.
If a new client detects an old server, a warning is printed. The main hazard there is that the client may want new features the server does not provide.
Starting with QCFractal v1.0, we should move to semver, so we could at least check major versions between client and server. This would allow us to remove the older versioned endpoints.
Changelog description
Removed forced version checks between client and server
Description
Remove client/manager version checks against what the server reports.
Starting in 0.51, backwards-incompatible changes to the API will be handled by changing the version in the URI (ie,
/api/v1/datasets->/api/v2/datasets). This will be done only on the endpoints that do change.The
v1API's will left in place, so older clients will still work with newer servers.If a new client detects an old server, a warning is printed. The main hazard there is that the client may want new features the server does not provide.
Starting with QCFractal v1.0, we should move to semver, so we could at least check major versions between client and server. This would allow us to remove the older versioned endpoints.
Changelog description
Removed forced version checks between client and server
Status