release 0.20.0

[michaeldwan]

Looks like 0.20.0 is mentioned in the changelog but hasn't been tagged yet -- is it ready for a release?

[kzys]

Yes. We will tag the release pretty soon!

[kzys]

We've just realized that SDK is currently not compatible with Firecracker's Vsock protocol change (firecracker-microvm/firecracker@a271d08#diff-1b131960ac0b33a6de812a32a990a882).

[jeromegn]

We've been having some trouble with reconnecting to a vsock, but only sometimes. This is a weird one, not sure if related. I can't replicate locally, this is only happening in our production setup afaict.

[kzys]

Thanks for reporting @jeromegn! Can you open an issue with the details of the problem? It may not be related, since the vsock change would break us 100%.

Regarding the vsock change, apparently we don't have to fix the SDK since vsock handling is mostly in firecracker-containerd side, but we have found that Firecracker 0.20.0 has another backward-incompatible change (firecracker-microvm/firecracker#1547).

[luxas]

Friendly ping on tagging the v0.20.0 release, for easier vendoring :)
Thanks for all your work!

[kzys]

We have released 0.20.0 finally! Regarding the backward incompatible change, it only affects errors and the fix has been merged into firecracker/master already.

https://github.com/firecracker-microvm/firecracker-go-sdk/releases/tag/v0.20.0