Skip to content

[Breaking change]: Legacy Mono and Emscripten JavaScript APIs are not exported to global namespace in Blazor WebAssembly applications #438

[Breaking change]: Legacy Mono and Emscripten JavaScript APIs are not exported to global namespace in Blazor WebAssembly applications

[Breaking change]: Legacy Mono and Emscripten JavaScript APIs are not exported to global namespace in Blazor WebAssembly applications #438

Triggered via issue November 15, 2024 18:59
Status Success
Total duration 12s
Artifacts

bcnotify.yaml

on: issues
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, timheuer/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, timheuer/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/