feat: (CM64) Allow component model resources to be represented by i64 as well as i32.
#6504
michael-weigeltmain.yml
on: pull_request
Matrix: Build wasm-tools
Matrix: Test
Matrix: Test the C API
Test (no-hash-maps)
3m 49s
Test with extra Cargo features
1m 56s
Test libdl.so
1m 13s
Test on WebAssembly
4m 34s
Rustfmt
38s
Fuzz
2m 29s
check
3m 58s
Check generated files are up-to-date
1m 13s
doc
7m 9s
clippy
1m 54s
verify-publish
2m 56s
maybe-trigger-tag
0s
Annotations
10 warnings
|
Build wasm-tools (wasm32-wasip1, ubuntu-latest, wasm32-wasip1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (x86_64-macos, macos-latest, x86_64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (riscv64-linux, ubuntu-latest, riscv64gc-unknown-linux-gnu, ./ci/docker/riscv64-...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (aarch64-linux, ubuntu-latest, aarch64-unknown-linux-gnu, ./ci/docker/aarch64-li...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (x86_64-linux, ubuntu-latest, x86_64-unknown-linux-gnu, ./ci/docker/x86_64-linux...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (x86_64-musl, ubuntu-latest, x86_64-unknown-linux-musl, ./ci/docker/x86_64-musl/...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (aarch64-macos, macos-latest, aarch64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (aarch64-musl, ubuntu-latest, aarch64-unknown-linux-musl, ./ci/docker/aarch64-mu...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (x86_64-windows, windows-latest, x86_64-pc-windows-msvc, -Ctarget-feature=+crt-s...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build wasm-tools (aarch64-windows, windows-11-arm, aarch64-pc-windows-msvc, -Ctarget-feature=+crt...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bins-aarch64-linux
|
5.65 MB |
sha256:79ab7d2872916f3c64b92b507b961ea805a7506ed71f9e24b8a1895c275705a2
|
|
|
bins-aarch64-macos
|
5.09 MB |
sha256:05f3ac7b2ea078839e9cbbcf7731d1220cc0dbe2d9cf8adfe4538eaf15cc278f
|
|
|
bins-aarch64-musl
|
5.7 MB |
sha256:2d494d69554167b4d6e431538b6dfda184e1c16dd33b48110556f3e2a9ce0d9f
|
|
|
bins-aarch64-windows
|
4.06 MB |
sha256:ee3d81697255f354c0a1bce9a6f2d067f484f6914c2c8b0f6c5ca5a81f3bf592
|
|
|
bins-riscv64-linux
|
6.06 MB |
sha256:b95781b745581dc8c8dfd655e1ab4d47bbe71bf14cf7b2c475f4692b579cb2ec
|
|
|
bins-wasm32-wasip1
|
3.62 MB |
sha256:d34eeda4b14a568e26c5bba2b698d1d98d64dbf26df31982bfb0aee44189f161
|
|
|
bins-x86_64-linux
|
5.69 MB |
sha256:aed161727e7c54e46943c90ae36a2239f074c5345d9eb4a3a949103b80df28ce
|
|
|
bins-x86_64-macos
|
5.49 MB |
sha256:7b4611711dfff3a2c0cbdf52cf7fd0d0a06d454873251ade7278f5c25fc7aade
|
|
|
bins-x86_64-musl
|
5.94 MB |
sha256:fd852e6a656408b8c455a4ffad05cc587dee92a8bce8be21a035526b75a75a29
|
|
|
bins-x86_64-windows
|
4.38 MB |
sha256:10fbbe5090464c2672a85f89b543a9068741e00afb3bf8472ee4c1a72a904df8
|
|