Skip to content

types: Force required fields on different transaction types #736

types: Force required fields on different transaction types

types: Force required fields on different transaction types #736

Triggered via pull request July 25, 2023 13:38
Status Success
Total duration 5m 1s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test.yaml

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

Annotations

2 warnings
build (3.10, 1.20.5, 0.8.20)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/setup-python@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 (3.11, 1.20.5, 0.8.20)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/