Skip to content

fix: ensure read-only values are resolved in post trie #207

fix: ensure read-only values are resolved in post trie

fix: ensure read-only values are resolved in post trie #207

Triggered via pull request September 28, 2023 09:59
Status Failure
Total duration 11m 26s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

go.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
test
Process completed with exit code 1.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. 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 uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/