v0.8.1

• Updated forta-core-go to take @aomerk's memory usage improvements in forta-network/forta-core-go#239
• Removed the unsafe.Pointer hack in gRPC message encoding
• Reusing top-level bot context to implement the "closed" state for the bot client
• Removing bot container images only during cleanups (not node exits)

What's Changed

• General improvements (memory, bot client, containers) by @canercidam in #745

Full Changelog: v0.8.0...v0.8.1

v0.8.0

Bot lifecycle management refactor

This release includes architectural changes to bot lifecycle management and internal messaging architecture, and general improvements to recent issues. The supervisor service has become the actor that detects assignment changes and drives state changes in the rest of the services.

More bot metrics and new system errors

To increase the observability on the internal issues, we reused previous bot metrics definitions and added bot lifecycle metrics. Some of these metrics signal the checkpoints in the lifecycle as well as mentioning the bot lifecycle errors and system errors.

Sending error messages is made possible by adding a new details field to metrics.

Other improvements

• Added back handling of initialize response errors (originally added in #724)
• Added cleanup step to bot lifecycle in order to remove unused bot resources
• Added cooldown to bot image pull retries and removed the infinite loop
• Preserved infinite loop for bot release image downloads

What's Changed

• Bot lifecycle management refactor by @canercidam in #726
• Add metrics to refactor by @stevenlanders in #738
• Clean up unused bots by @canercidam in #735
• Handle error response from initialize and detect nil responses by @canercidam in #736
• Close bot clients and replace in pool by @canercidam in #739
• Add cooldown to image pulls by @canercidam in #737
• Set the supervisor strategy version as RFC3339 timestamp by @canercidam in #741
• Copy details into metrics summary by @stevenlanders in #740
• Make release image download retry by @canercidam in #742

Full Changelog: v0.7.16...v0.8.0

v0.7.16

What's Changed

• Add latest release manifest as 'latest' to distribution S3 by @canercidam in #730
• Surface image check errors by @stevenlanders in #731
• Remove the network on bot stops by @aomerk in #732
• Detach containers before removing network by @aomerk in #733
• Retry initialization responses with error status by @aomerk in #724

Full Changelog: v0.7.15...v0.7.16

v0.7.15

Fix high memory consumption in forta-scanner container

What's Changed

• Update core lib by @stevenlanders in #728

Full Changelog: v0.7.14...v0.7.15

v0.7.14

Added more bot lifecycle metrics

What's Changed

• Add metrics for troubleshooting by @stevenlanders in #727

Full Changelog: v0.7.13...v0.7.14

v0.7.13

Minor patches to the bot lifecycle

What's Changed

• Remove subscriptions from nuked bots by @aomerk in #708
• Improve bot initialization by @aomerk in #718
• Set bot deploy context timeout per deployment by @aomerk in #720
• Scanner does not re deploy bots on deployment failures by @aomerk in #719
• Wait for agent initalization to start processing by @aomerk in #721

Full Changelog: v0.7.12...v0.7.13

v0.7.12

Reducing the pressure on the bot list mutex

# @begin release_config
deprecationPolicy:
  supportedVersions:
    - v0.7.12
  activatesInHours: 138
# @end release_config

What's Changed

• Use RLock for handleStatusRunning by @aomerk in #717

Full Changelog: v0.7.11...v0.7.12

v0.7.11

Reverting the change that enforces the latest bot list every 15 seconds

# @begin release_config
deprecationPolicy:
  supportedVersions:
    - v0.7.11
  activatesInHours: 130
# @end release_config

What's Changed

• Revert "Always publish latest bots" by @aomerk in #707

Full Changelog: v0.7.10...v0.7.11

v0.7.10

Bug fix to bot memory limit

What's Changed

• Fix the memory limit in bots by @canercidam in #714

Full Changelog: v0.7.9...v0.7.10

v0.7.9

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