Skip to content

Releases: forta-network/forta-node

v0.8.11

11 Jul 15:30
8a48afd
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.10...v0.8.11

v0.8.10

11 Jul 13:38
d0c2040
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.9...v0.8.10

v0.8.9

21 Jun 22:04
cb60303
Compare
Choose a tag to compare

What's Changed

  • Add more auto-update telemetry data and simplify release scheduling by @canercidam in #775

Full Changelog: v0.8.8...v0.8.9

v0.8.8

19 Jun 20:14
c3eba88
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.7...v0.8.8

v0.8.7

16 Jun 19:48
167a8b3
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.6...v0.8.7

v0.8.6

15 Jun 17:26
2e9e059
Compare
Choose a tag to compare

What's Changed

  • Use backoff retries for registry calls by @aomerk in #770
  • Add new system status metric type and use it for bot assignments by @canercidam in #769

Full Changelog: v0.8.5...v0.8.6

v0.8.5

14 Jun 10:15
b33c6b0
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.4...v0.8.5

v0.8.4

13 Jun 18:59
77ecf6a
Compare
Choose a tag to compare

Shard ID fixes

We noticed a problem about some shard IDs failing to calculate using free APIs (polygon-rpc.com) and optimized the assignment list loading using our go-multicall library. This also helps reducing the load on the registry APIs and increases the general consistency.

Another problem that is fixed along with this release is the mixup in the shard ID that appears in the metrics. This helps avoid confusion while monitoring how the network operates bot shards.

New forta status all subcommand

Now instead of using forta status --show all --format oneline, operators can simply use forta status all!

More metrics

We added more metrics to increase visibility in the issues:

  • Errors during loading assigned bots
  • Bot alert processing response validation errors

Reduced docker pull concurrency

To remedy the pull retry issues visible in some nodes, we have reduced the concurrency to pull one image at a time and increased the timeout from 5 minutes to 10 minutes. This will help speed up the eventual start of bots.

Local mode improvements

  • Fixed standalone mode which was broken starting with v0.8.0
  • Fixed the zero block error which happens when working with Hardhat
  • Disabled the trace requirement for all chains

Other improvements

  • Fixed bot attachment bug that happens during graceful auto-upgrades
  • Started the JSON-RPC API health checker
  • Pinned docker/docker (moby/moby) version to the minimum requirement v20.10.x after dependency update issues
  • Reduced test coverage fluctuation between test runs (due to concurrent parts)

What's Changed

Full Changelog: v0.8.3...v0.8.4

v0.8.3

07 Jun 11:54
de4627b
Compare
Choose a tag to compare

Fixed the bot logs bug introduced in v0.8.0

What's Changed

Full Changelog: v0.8.2...v0.8.3

v0.8.2

06 Jun 15:22
d91b541
Compare
Choose a tag to compare
# @begin release_config
deprecationPolicy:
  supportedVersions:
    - v0.8.2
    - v0.8.1
  activatesInHours: 36
# @end release_config

What's Changed

  • Use jq instead of sed to get the IPFS CID from the upload output by @canercidam in #746

Full Changelog: v0.8.1...v0.8.2