forta-network/forta-node v0.7.9

on GitHub

Deprecation policy

Starting with this version, Forta node releases may contain release settings which mention the deprecation policy. As we make fixes and add new features to node software, we are trying to ensure that all of the network is running only the supported versions so the detection bots can be run reliably and use the latest features.

If no deprecation policy is mentioned, all nodes will be expected to switch to the latest version within 7 days after the release. The nodes which keep running old versions of the software after this period may start experiencing low SLA scores.

A better forta version command

Since Forta containers can be dynamically updated and can have newer versions than the installed CLI, we updated the forta version command to give you a better understanding about what versions your node is running at any given time. Example output:

{
  "cli": {
    "commit": "ef621ff8cf9e467e021630a6c0367214883e1130",
    "ipfs": "QmbnNB1iyrNthzSptqxXkdz4RHfU3g5Y7QesLhbmv5xrF2",
    "version": "v0.1.2"
  },
  "containers": {
    "commit": "ef621ff8cf9e467e021630a6c0367214883e1130",
    "ipfs": "QmbnNB1iyrNthzSptqxXkdz4RHfU3g5Y7QesLhbmv5xrF2",
    "version": "v0.2.3"
  }
}

General bug fixes

• Fixed a mutex-related bug that causes input lags, low SLA scores and bot update problems
• Refactored the updater and increased robustness

# @begin release_config
deprecationPolicy:
  supportedVersions:
    - v0.7.9
  activatesInHours: 72
# @end release_config

What's Changed

• Use the config in release description in release manifest by @canercidam in #704
• Unblock poolagent.Agent's mutex and avoid hangs by @canercidam in #711
• Add missing env vars to compose file by @canercidam in #712
• Refactor updater to split store and service by @stevenlanders in #709
• Display both CLI and container version in 'forta version' output by @canercidam in #713

Full Changelog: v0.7.8...v0.7.9