Use `almalinux:8` instead of `centos:7` docker image for release builds (#108)* Update the binary-compatible-builds action from Wasmtime * Use `almalinux:8` as base image for x86_64-linux CI doc
Use `almalinux:8` instead of `centos:7` docker image for release builds (#108)* Update the binary-compatible-builds action from Wasmtime * Use `almalinux:8` as base image for x86_64-linux CI docker image The `centos:7` image hit end of life, so we need something new. Similar to https://github.com/bytecodealliance/wasmtime/pull/8892 in Wasmtime. * Allos `cfg(fuzzing)` * Remove dead code ever since module-linking support was removed * set global npm config with sudo in ci
show more ...
Move to using the same cross-compiling workflow as wasmtime which enables binary compatible builds and compiles for more platformsThese prebuilt binaries will eventually be used within a wizer npm
Move to using the same cross-compiling workflow as wasmtime which enables binary compatible builds and compiles for more platformsThese prebuilt binaries will eventually be used within a wizer npm package (which itself will be used within the `@fastly/js-compute` npm package).I've tested both the macos builds and they are workingI don't have a windows machine to test on and I don't have an x86_64 linux machine to test on unfortunatelyaarch64-linux and s390x-linux are commented out due to build errors these errors are solved in a newer version of wasmtime, when wizer updates to the newer wasmtime then we should uncomment these builds