This brings wasmCloud up to date with the latest release, v1.2.1.
It also removes v0.82.0, because realistically no-one should be using that as it is not really supported or compatible with the latest the v1.x line of wasmCloud releases.
How to use
Once the image is built, you can employ the following configuration ignition configuration (replacing with the appropriate value) to consume it as outlined in the updated README.
Testing done
I've built and deployed this on to a DigitalOcean Droplet to validate that it works as expected:
Flatcar Container Linux by Kinvolk stable 3975.2.1 for DigitalOcean
core@flatcar-sysext-01 ~ $ wasmcloud --version
wasmcloud 1.2.1
[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
[ ] Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.
Update wasmCloud to 1.2.1
This brings wasmCloud up to date with the latest release, v1.2.1.
It also removes
v0.82.0, because realistically no-one should be using that as it is not really supported or compatible with the latest thev1.xline of wasmCloud releases.How to use
Once the image is built, you can employ the following configuration ignition configuration (replacing with the appropriate value) to consume it as outlined in the updated README.
Testing done
I've built and deployed this on to a DigitalOcean Droplet to validate that it works as expected:
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.