Release Notes

Table of Contents

• Airnode
• Beacons
• OIS

Use this page as a checklist when creating a new release for any versioned documentation set. It may be necessary to reference other pages in the /dev document set.

TODO:

It is possible to use a $themeConfig variable such as airnodeLatest to use in the path of a link. However they canot be used in markdown links, only with router-link.

Example: Link

This could be used when a document set sends the user to another versioned doc set where the latest version is desired.

It is not useful when links go to a GitHub repo README since the versions must match a tag at the repo.

Airnode

• Be sure all links to Github use the proper tag. Look for use of master, main or a previous tag such as v0.4.

• Check that the tutorial zip files are up-to-date.

• Update the Docker deployer image versions in /.vuepress/components/DockerImageVersions.vue.

• Update the versions in the config.js files. See the doc Versioning for help.

• Look for older Airnode versions such as 0.4.0 in configuration files.

• The OIS document set has links back to Airnode. Look for an older tag such as v0.4 and update as needed. There is at least one link to the Airnode repo as well that uses a tag (such as v0.4).

• The Beacons document set has links back to Airnode. Look for an older tag such as v0.4 and update as needed.

Beacons

To-Be-Update

This section will get updated when the next release of Beacons is ready.

OIS

To-Be-Update

This section will get updated when the next release of OIS is ready.