frequency-chain/metadata-portal

Fix Deploy Workflow

Closed this issue · 7 comments

The check deployment action fails with:

error decoding response body: missing field `version` at line 21 column 5

The verifier public key is incorrect.

error parsing context type
[2023-06-01T19:50:29Z ERROR] failed to verify frequency-rococo_metadata_35.apng: public key mismatch! Expected 4402e2896c0aa61006b223f7f9b5e3703080c2f172642fd0c43de9892df76d79, got d6a3105d6768e956e9e5d41050ac29843f98561410d3a47f9dd5b3b227ab8746

@rlaferla Did we overwrite the key with the upstream upgrade?

@wilwade No, the key was not overridden.

The issue is that the data.json from the old Metadata Portal is still live and the deployment check is comparing it against a freshly generated data.json (which has a slightly different format.). It does this comparison to see if the data is up-to-date or if it needs to redeploy.

New portal successfully deployed. Need to refresh the data and add some additional documentation.