Upstream has moved ahead of public/api/versions.json for keys the bump job
deliberately does not change on its own. Nothing here is a verified fact —
each needs a human to confirm it before public/api/versions.json is edited.
Editing that one file updates every page that renders the value.
Deployed network versions — confirm the network actually upgraded
chain_testnet and chain_mainnet record the release each network is
currently running. The figure below is only the newest allora-chain
tag: a tag does not mean either network upgraded, and the two networks
are routinely on different releases. Confirm the deployed version per
network — the upgrade announcement, or querying the network itself — and
update only the keys that really moved.
public/api/networks.json records the same fact per network in
deployed_version, so update it in the same commit — yarn checkversions
fails while the two files disagree.
| Key |
Current |
Upstream |
Source |
chain_mainnet |
v0.16.0 |
v0.17.0 |
GitHub releases |
This issue is updated in place while these findings hold. Closing it is
respected: it is not reopened until the proposed versions themselves change.
Upstream has moved ahead of
public/api/versions.jsonfor keys the bump jobdeliberately does not change on its own. Nothing here is a verified fact —
each needs a human to confirm it before
public/api/versions.jsonis edited.Editing that one file updates every page that renders the value.
Deployed network versions — confirm the network actually upgraded
chain_testnetandchain_mainnetrecord the release each network iscurrently running. The figure below is only the newest
allora-chaintag: a tag does not mean either network upgraded, and the two networks
are routinely on different releases. Confirm the deployed version per
network — the upgrade announcement, or querying the network itself — and
update only the keys that really moved.
public/api/networks.jsonrecords the same fact per network indeployed_version, so update it in the same commit —yarn checkversionsfails while the two files disagree.
chain_mainnetv0.16.0v0.17.0This issue is updated in place while these findings hold. Closing it is
respected: it is not reopened until the proposed versions themselves change.