@openeo/js-commons starting with version 2.0.0 will not support migrations any longer, see https://github.com/Open-EO/openeo-js-commons/issues/8
Migrations will be implemented for v1.0.0+ in the JS client directly, including all requests, responses and other aspects like path changes. The JS client will always return responses in a way that they are compliant to the latest (supported) API version. Libraries like the openEO Hub are expected to use the JS client for requests, migrations etc.
m-mohr
commented
3 years ago
@openeo/js-commons starting with version 2.0.0 will not support migrations any longer, see https://github.com/Open-EO/openeo-js-commons/issues/8 Migrations will be implemented for v1.0.0+ in the JS client directly, including all requests, responses and other aspects like path changes. The JS client will always return responses in a way that they are compliant to the latest (supported) API version. Libraries like the openEO Hub are expected to use the JS client for requests, migrations etc.