Skip to content

fix: use SHA384 for ECDSA P384 #1003

fix: use SHA384 for ECDSA P384

fix: use SHA384 for ECDSA P384 #1003

Triggered via pull request April 2, 2024 08:52
Status Success
Total duration 3m 39s
Artifacts

ci.yml

on: pull_request
linting  /  govulncheck
20s
linting / govulncheck
linting  /  golangci-lint
11s
linting / golangci-lint
Matrix: examples / client
Matrix: examples / multirepo
Matrix: examples / repository
Matrix: examples / root-signing
Matrix: examples / tuf-client-cli
Matrix: tests / Run
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Cannot open: File exists
linting / golangci-lint
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
tests / Run (windows-latest)
Codecov: Failed to properly upload report: The process 'D:\a\_actions\codecov\codecov-action\54bcd8715eee62d40e33596ef5e8f0f48dbbccab\dist\codecov.exe' failed with exit code 1