update ci write permissions (#120)

Fix Intel Mac CI builds. (#118)

* Fix Intel Mac CI builds.

We build both x86-64 and aarch64 ("Intel Mac" and "Apple Silicon Mac")
binaries for wizer in CI on the `macos-latest` CI runner. Histor

Fix Intel Mac CI builds. (#118)

* Fix Intel Mac CI builds.

We build both x86-64 and aarch64 ("Intel Mac" and "Apple Silicon Mac")
binaries for wizer in CI on the `macos-latest` CI runner. Historically,
this runner was an x86-64 machine, so while we could do a direct compile
for x86-64 binaries, we added a target override for `aarch64-darwin` for
the aarch64 builds to force a cross-compile.

When GitHub switched macOS CI runners to aarch64 (ARM64) machines
somewhat recently, the `macos-latest` runner image began producing
aarch64 binaries by default, and the target override for
cross-compilation became meaningless (redundant). As a result, *both* of
our x86-64 and aarch64 macOS binary artifacts contained aarch64
binaries. This is a problem for anyone running an Intel Mac.

This PR switches the CI config to specify a cross-compilation of x86-64
binaries, so each target builds its proper architecture.

* Use actions/upload-artifact v4

* Use v4 of actions/download-artifact too

show more ...

release: fix version updating (#114)

fixup deploy workflow (#112)

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 ...

release: add npmrc to ensure publish permissions (#107)

* release: add npmrc to ensure publish permissions

* use configuration instead

* use global config

fix release workflow

Update release.yml

ci: publish the npm packages when a new tag is pushed

ci: add aarch64-unknown-linux-gnu and s390x-unknown-linux-gnu as new precompiled artifact targets

ci: add aarch64-unknown-linux-gnu and s390x-unknown-linux-gnu as new test targets

Enable binary releases for AArch64 and s390x

Now that Wasmtime has been updated these should theoretically work
according to the prior comments.

Move to using the same cross-compiling workflow as wasmtime which enables binary compatible builds and compiles for more platforms

These 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 platforms

These 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 working
I don't have a windows machine to test on and I don't have an x86_64 linux machine to test on unfortunately

aarch64-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

show more ...

Add release workflow which builds for multiple operating systems and architectures

These can be used by people who want to install wizer without having to compile it themselves.
One such use-case wo

Add release workflow which builds for multiple operating systems and architectures

These can be used by people who want to install wizer without having to compile it themselves.
One such use-case would be the fastly compute runtimes which install wizer in their CI environments.

show more ...

Merge pull request #52 from fitzgen/bump-to-version-1.4.0

Bump to version 1.4.0