SONIC: Releases
New version numbers released each day across the mirrored repositories.
Why use it. Releases are when the developers' work reaches users and node operators. How to read it. Each repository's version number counts once, on the day of its first tag (its first release candidate, if any), however many builds, networks or packages are tagged with it. Clients with their own version numbers each count.
Calculation. Version numbers are the dotted numbers in the repositories' tag names (v1.15.1-rc.0 counts as 1.15.1), dated by the tag's own date (the commit's date for lightweight tags). Tags without one (build, CI or date-named tags) are not releases here. A tag two of the asset's repositories share counts once, and tags of commits inherited from other projects are left out. Source: CryptoKeyhole's own mirrors of 4 public repositories of Sonic on GitHub, fetched every 30 minutes. 0xsoniclabs/sonic: the Sonic node. 0xsoniclabs/carmen: Carmen, the node's state database. 0xsoniclabs/tosca: Tosca, the node's EVM interpreters. 0xsoniclabs/sonic-sfc: the network's staking and system contracts. History starts at the first counted commit, on 16 January 2017. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.