The exchangerate.host API service was recently updated (seemingly without warning) and put behind a paywall. As part of the updates, all requests now require an API key to be passed as a query parameter. The endpoints, accepted query parameters, and response structure have also all been updated.
This PR makes some updates to the package so that we can interact with the newer version of this API.
Breaking change?
I'm not entirely sure whether this is a breaking change or not 🤔
This change will require human intervention (adding the API key to the .env file) which leads me to think it'd be a major version bump.
However, this fix is needed due to an external change and anyone using this package won't be able to interact with this API at the moment. So I think this means it can be treated as a bug fix (patch version bump) rather than a breaking change (major version bump).
The
exchangerate.hostAPI service was recently updated (seemingly without warning) and put behind a paywall. As part of the updates, all requests now require an API key to be passed as a query parameter. The endpoints, accepted query parameters, and response structure have also all been updated.This PR makes some updates to the package so that we can interact with the newer version of this API.
Breaking change?
I'm not entirely sure whether this is a breaking change or not 🤔
This change will require human intervention (adding the API key to the
.envfile) which leads me to think it'd be a major version bump.However, this fix is needed due to an external change and anyone using this package won't be able to interact with this API at the moment. So I think this means it can be treated as a bug fix (patch version bump) rather than a breaking change (major version bump).