CI

runtime: fix canonical call context and drop delivery semantics #461

Sign in to view logs

Triggered via pull request September 14, 2026 05:30

lannbot

opened #375

fix/wasmtime-async-semantics

Status Success

Total duration 6m 21s

Artifacts –

ci.yml

on: pull_request

Matrix: core

release / release

Annotations

10 warnings

core (ubuntu-24.04)

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

core (ubuntu-24.04): runtime/src/exec/boundary.ts#L1696

unable to analyze dynamic import

core (ubuntu-24.04): runtime/src/exec/boundary.ts#L1667

unable to analyze dynamic import

core (ubuntu-24.04): runtime/src/exec/boundary.ts#L222

unable to analyze dynamic import

core (ubuntu-24.04): ct-runner/src/main.ts#L130

unable to analyze dynamic import

core (ubuntu-24.04-arm)

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

core (ubuntu-24.04-arm): runtime/src/exec/boundary.ts#L1696

unable to analyze dynamic import

core (ubuntu-24.04-arm): runtime/src/exec/boundary.ts#L1667

unable to analyze dynamic import

core (ubuntu-24.04-arm): runtime/src/exec/boundary.ts#L222

unable to analyze dynamic import

core (ubuntu-24.04-arm): ct-runner/src/main.ts#L130

unable to analyze dynamic import