Skip to content

Releases: api3dao/airnode

v0.14.2

02 Jul 05:30
@dcroote dcroote
v0.14.2
3b81fd6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.14.2 Latest
Latest

What's Changed

Full Changelog: v0.14.1...v0.14.2

Contributors

acenolaza and dcroote
Assets 2
Loading

v0.14.1

29 Mar 05:33
@dcroote dcroote
v0.14.1
9e3ddd0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.14.1

What's Changed

This patch release bumps api3/ois to v2.3.2 to fix a bug where the API call could not be skipped when using pre/post-processing v2. To fix a Docker packaging issue, Node.js has been updated from Node.js 18.14.0 to 18.19.1 within Docker images.

Changelog

Full Changelog: v0.14.0...v0.14.1

Contributors

dcroote
Assets 2
Loading

v0.14.0

21 Jan 22:13
@dcroote dcroote
v0.14.0
035bb02
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.14.0

What's Changed

This release includes contract deployments to additional chains, breaking changes to the OEV gateway, the addition of a version 2 of pre-processing and post-processing in conjunction with the release of OIS v2.3.1, removal of chainNames and networks exports from references.json of airnode-protocol, and other various improvements and bug fixes.

For additional detail, see the Airnode v0.14 migration guide.

Changelog

New Contributors

Full Changelog: v0.13.0...v0.14.0

Contributors

renovate, dcroote, and 3 other contributors
Assets 2
Loading

v0.13.0

31 Oct 06:41
@dcroote dcroote
v0.13.0
0f173c2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.13.0

What's Changed

This release includes contract deployments to additional chains, a fix for the HTTP gateway response, less restricted OIS endpoint parameters, and various other improvements and bug fixes.

Release highlights

  • Airnode protocol contracts were deployed on the following chains: linea, linea-goerli-testnet, mantle, mantle-goerli-testnet, base, base-goerli-testnet, polygon-zkevm, and polygon-zkevm-testnet.
  • The HTTP Gateway response has been harmonized so that the API call response, after undergoing any post-processing, will be present in the rawValue field independent of encoding success or failure.
  • In conjunction with the OIS bump to v2.2, endpoint parameters now do not have to be mapped to operation parameters.

Changelog

New Contributors

Full Changelog: v0.12.0...v0.13.0

Contributors

amarthadan, renovate, and 5 other contributors
Assets 2
Loading

v0.12.0

25 Jul 10:36
@amarthadan amarthadan
v0.12.0
07701d7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.12.0

What's Changed

This release brings sensible defaults for some of the configuration fields, changes to the HTTP gateways' inner workings, and many other improvements and bug fixes.

Release highlights

  • Fields specifying AirnodeRrpV0 and RequesterAuthorizerWithErc721 contract addresses on chains for which there is an API3 deployment are now optional.
  • fulfillmentGasLimit field is now optional. If no value is assigned, then Airnode will dynamically determine a callback gas limit.
  • There is no longer a hardcoded limit to the maximum number of sponsor wallet requests processed each cycle.
  • The following changes were made to the HTTP gateway:
    • Data is returned from successful API calls that fail response processing. For an example see the HTTP Gateways page.
    • Reserved parameters are inaccessible in response pre/post-processing. This is only relevant if reserved parameters are being modified in pre/post-processing (advanced use case).
  • The value for a fixedOperationParameters object is now allowed to be any type, including an object. This has not changed since v0.11.2, but has changed since v0.11.0 and v0.11.1 for which it was only allowed to be a string.
  • Endpoint ID now must be a hash of the OIS title and endpoint name. Previously it was only recommended.

Changelog

New Contributors

Full Changelog: v0.11.0...v0.12.0

Contributors

cserb, amarthadan, and 6 other contributors
Assets 2
Loading

v0.11.2

28 Jun 13:43
@amarthadan amarthadan
v0.11.2
cd8ace8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.11.2

What's Changed

Full Changelog: v0.11.1...v0.11.2

Contributors

amarthadan and dcroote
Assets 2
Loading

v0.11.1

25 May 14:18
@amarthadan amarthadan
v0.11.1
562da0c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.11.1

What's Changed

Full Changelog: v0.11.0...v0.11.1

Contributors

amarthadan and dcroote
Assets 2
Loading

v0.11.0

11 Apr 09:35
@amarthadan amarthadan
v0.11.0
a379bc0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.11.0

What's Changed

This release brings two new types of authorizers, a new gateway to support our OEV initiative, and many other improvements and bug fixes.

Release Highlights

  • The Node.js version of Airnode was upgraded from 14 to 18.
  • Node.js version of the pre- and post-processing environments is dictated by the Node.js version of Airnode.
  • The two new authorizers, requesterAuthorizersWithErc721 and crossChainRequesterAuthorizersWithErc721, that enable request authorization using ERC721 tokens were added. For further details, see the Authorizers page in the documentation.
  • There's a new gateway available called the OEV gateway. You can read more about this feature in its documentation.
  • The heartbeat payload now includes Airnode's deployment ID.
  • The coingecko-signed-data and coingecko-testable HTTP gateway airnode-examples integrations have been combined into a single coingecko-http-gateways integration.

Changelog

New Contributors

Full Changelog: v0.10.0...v0.11.0

Contributors

amarthadan, renovate, and 4 other contributors
Assets 2
Loading

v0.10.1

11 Apr 09:17
@amarthadan amarthadan
v0.10.1
5475a30
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.10.1

What's Changed

Full Changelog: v0.10.0...v0.10.1

Contributors

amarthadan
Assets 2
Loading

v0.10.0

07 Feb 12:44
@amarthadan amarthadan
v0.10.0
be1e68e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.10.0

What's Changed

This release brings new reserved parameters, a new type of authorizers, and many improvements for Deployer CLI.

Release Highlights

  • OIS version bump
  • Field apiKey was removed from the gateway configuration sections. Gateway URLs now contain a randomly generated UUID serving as an authentication mechanism.
  • Field nodeSettings.heartbeat.id was removed from the heartbeat configuration. The ID is no longer needed to recognize which Airnode is sending the heartbeat request as the payload is signed by the Airnode and the Airnode's public key can be recovered from the signature.
  • The command airnode-deployer remove-with-deployment-details no longer exists and was replaced by a new command airnode-deployer remove <deployment ID>. In order to remove the Airnode deployment with this command, you need to provide a deployment ID. You can find deployment ID in the receipt.json file for a given deployment or via airnode-deployer list command.
  • Allowing to skip API calls to just run pre/post processing. See the OIS documentation for more information.
  • There are two new reserved parameters available, _gasPrice and _minConfirmations. You can read more about how and what are they used for in the documentation.
  • We now support a new type of authorizer, a cross-chain authorizer. Read more about when it makes sense to use it and how in the documentation.
  • Airnode's Deployer CLI went through multiple changes, improving the user experience. There are four additional commands, list, info, rollback and fetch-files to help you interact with your deployments more easily. You can read all about the new features in the documentation.
  • In order to provide a better sense of Airnode behavior and improve the visibility of request logs within cloud provider monitoring services, the log level specified by nodeSettings.logLevel within config.json has been changed from INFO to DEBUG for airnode-examples integrations. Similarly, integration deployment commands are now run with the --debug flag.

Migration Guide

Please refer to the Airnode v0.9 to v0.10 migration guide for changes required to your config.json to support this version of Airnode.

Changelog

New Contributors

Full Changelog: v0.9.0...v0.10.0

Contributors

amarthadan, renovate, and 7 other contributors
Assets 2
Loading