Fix JavaScript error when a JSON-RPC response is generated while a chain is removed #4520
deploy.yml
on: pull_request
build-push-docker-image
4m 59s
npm-publish
1m 40s
deno-publish
1m 38s
crates-io-publish
1m 48s
build-js-doc
1m 50s
build-rust-doc
56s
build-tests-coverage
8m 41s
all-deploy
0s
Annotations
5 warnings
deno-publish
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
deno-publish
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deno-publish
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deno-publish
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deno-publish
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
code-coverage-report
Expired
|
5.5 MB |
|
javascript-documentation
Expired
|
107 KB |
|
rust-documentation
Expired
|
8.47 MB |
|