The 0.3.37 release of discovery-node focused on improving service resiliency after after a network issue including improved logging, updated max number of blocks that can be reverted. In addition, the discovery node should no longer stall during indexing the data contracts like before preferring to skip errors as long as all nodes in network wide and reconcile them later.
Full Changelog:
[0e626ee] - Include strategy version in trending cache keys (#1549)
[cb29da6] - Bump to v0.3.37 (#1546)
[fe85595] - Add trending nm (#1545)
[73cbd23] - Add Solana configs (#1542)
[a5ac8d9] - Support feeling lucky? (#1539)
[0d399f5] - Prevent indexing from blocking (#1528)
[8c3be50] - Dump visited timestamps for agg metrics as each node is visited (#1529)
[0dd2609] - Fix playlist library check (#1534)
[3b28518] - Playlist library (#1508)
[0161cc6] - Limit max number of blocks to revert + improve logging (#1525)
[ad556d8] - Sliced revert blocks (#1524)
[3e16e33] - Add a signer group config to discovery provider (#1515)
[31067db] - Add playlist updates (#1499)
[e7def4a] - Bump to v0.3.36 (#1498)
[37925c1] - Add migration to repair damaged segment orders (#1497)
[6de2a9f] - Adds indexing tests (#1477)