Mainnet 22 (emergency spork)

The epoch transition on Flow mainnet failed on 2/16 due to an issue with the Flow staking contract. The issue was identified and fixed. However, to resume regular epoch operation, Flow mainnet has to be sporked.

No other components and features were affected and are working as expected. Only epoch operation was affected.

Epoch

• Re-enable Epoch Integration Tests by @jordanschalm in #3835
• [v0.29] Remove requirement that weight > 0 in EpochSetup validation by @jordanschalm in #3935

Access Node

• [Access Client] Set message received limits - v0.29 backport by @peterargue in #3858
• [GRPC] Add cli flag for grpc max message size - v0.29 backport by @peterargue in #3893
• [Access] Fix panic converting execution data to protobuf messages by @peterargue in #3892
• [Access] Backport error reporting and rest metrics - v0.29 by @peterargue in #3929

Active Pacemaker

• Start pacemaker before processing pending blocks by @jordanschalm in #3859

Auth account

• Enable account linking / AuthAccount capabilities on all networks except Mainnet by @turbolent in #3910
• Enable Account Linking - Fix by @janezpodhostnik in #3920

Spork improvements

• 0.29 log invalid vote in bootstrap finalize by @zhangchiqing in #3936

Networking

• [Networking] Logging of libp2p Resource Limits at Node Startup - v0.29 by @yhassanzadeh13 in #3952

Misc

• Upgrade core contracts - port to v0.29 by @janezpodhostnik in #3770

Full Changelog: v0.29.7...v0.29.13