Upgrading Kubo from 0.15 to 0.28

[livid]

There was an IPNS issue starting in version 0.16 that prevented us from upgrading:

https://discuss.ipfs.tech/t/ipfs-name-resolve-does-not-always-return-the-freshest-cid-for-ipns-on-kubo-0-20-0/16624

Now it seems to be fixed, and there is a new feature, ipfs key sign, which could be useful in some new applications:

https://github.com/ipfs/kubo/releases/tag/v0.25.0

So, we began the work to upgrade the bundled Kubo from version 0.15 to the latest, 0.28.

[livid]

I hope this upgrade can fix #338 too.

[kailuo]

Implemented a basic auto migration process in this branch: https://github.com/Planetable/Planet/tree/ipfs-migration, should take care of upgrading existing Kubo binary from version 0.15.0 to 0.28.0 ( repo version 12 -> 15 )

[2color]

We've shipped a lot of fixes since Kubo 0.15 and the latest 0.32.1 release is packed with some cool features, e.g. AutoTLS. It should also fix #338.

Did you have any problems upgrading?

[livid]

We've shipped a lot of fixes since Kubo 0.15 and the latest 0.32.1 release is packed with some cool features, e.g. AutoTLS. It should also fix #338.

Did you have any problems upgrading?

Hey @2color, thanks for taking a look at our project.

When 0.29 was out, during our testing, it seemed that IPNS resolve issue was still consistently happening:

https://discuss.ipfs.tech/t/ipfs-name-resolve-does-not-always-return-the-freshest-cid-for-ipns-on-kubo-0-20-0/16624/8

So, we did not upgrade.

[2color]

Do you have any specific IPNS name that I can test?

[livid]

Today I tested again with this IPNS powered ohlife.eth.limo:

/ipns/k51qzi5uqu5dhbdxrvoeqy96c3krp2t1d9hfscjyn2mwts5f1w8f1sq99xwh3r

Very happy to report it seems the unexpected behavior is gone!

Below is what I got today:

Now, with the same 0.29 installation I used earlier, it can resolve consistently.

Previously in June, like in the screenshot below, a stale result pops from time to time. It was like a result was cached somewhere, and Kubo just used it.

@kailuo and I will do more testing with the latest 0.31 and restart our upgrading efforts. Thank you @2color!