Skip to content
Go

lib: use json unmarshal instead of jmespath #994

Sign in to view logs

lib: use json unmarshal instead of jmespath

lib: use json unmarshal instead of jmespath #994

Triggered via pull request January 4, 2024 08:14
@JacksonTianJacksonTian
opened #917
styles
Status Success
Total duration 5m 35s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

go.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
build (macos-12)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
build (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/