# Migration Guide

The following guide assumes a valid v0.8.x config.json file. All changes listed below will need to be implemented in order to migrate to Airnode v0.9.x. This document is written in a way that will preserve existing behaviour with earlier Airnode versions.

The document also mentions changes of the user facing services related to Airnode, such as airnode-deployer, airnode-admin and more.

# Summary

ois[n].oisFormat updated to "1.2.0".
nodeSettings.nodeVersion updated to "0.9.2".
airnode-deployer remove-with-deployment-details now accepts a full --airnode-address argument instead of the short airnode address (--airnode-address-short).
We recommend using Sepolia and Goerli testnets instead of Rinkeby, Ropsten, and Kovan.

# Details

ois[n].oisFormat

Updated to "1.2.0"

{
-  "oisFormat": "1.1.2"
+  "oisFormat": "1.2.0"
}

1
2
3
4

nodeSettings.nodeVersion

Updated to "0.9.2"

{
-  "nodeVersion": "0.8.1"
+  "nodeVersion": "0.9.2"
}

1
2
3
4

airnode-deployer remove-with-deployment-details accepts --airnode-address parameter

In Airnode v0.9.x the airnode-deployer underwent an internal refactor to improve cloud provider deployments. The only user facing change is that the deployer uses the full Airnode address instead of the shortened one when executing the remove-with-deployment-details command.

- docker run -it --rm \
-   -v "$(pwd):/app/config" \
-   api3/airnode-deployer:0.8.1 remove-with-deployment-details \
-   --airnode-address-short abd9eaa \
-   --stage dev \
-   --cloud-provider gcp \
-   --projectId myAirnode101 \ ← GCP only
-   --region us-east1
+ docker run -it --rm \
+   -v "$(pwd):/app/config" \
+   api3/airnode-deployer:2 remove-with-deployment-details \
+   --airnode-address 0xabd9eaa588B6818Ac4C32c5e9b31962E351Cd39F \
+   --stage dev \
+   --cloud-provider gcp \
+   --projectId myAirnode101 \ ← GCP only
+   --region us-east1

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Recommended testnets to use are now Sepolia and Goerli

The Rinkeby, Ropsten, and Kovan testnets have been deprecated and will be removed. Etherscan has also discontinued or is in the process of discontinuing their blockchain explorer for each. You can read more details on the ethereum blog (opens new window).

← Cloud Resources