Skip to content

fix(deps): update module github.com/ory/x to v0.0.641 #374

fix(deps): update module github.com/ory/x to v0.0.641

fix(deps): update module github.com/ory/x to v0.0.641 #374

Triggered via pull request July 5, 2024 15:09
Status Failure
Total duration 53s
Artifacts

docker-build.yaml

on: pull_request
docker-build
43s
docker-build
Trivy fs scan
20s
Trivy fs scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
docker-build
buildx failed with: ERROR: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=${TARGETOS:-linux} GOARCH=${TARGETARCH} go build -a -o manager cmd/main.go" did not complete successfully: exit code: 1
Trivy fs scan
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, github/codeql-action/upload-sarif@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Trivy fs scan
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Trivy fs scan
Unexpected input(s) 'security-checks', valid inputs are ['entryPoint', 'args', 'scan-type', 'image-ref', 'input', 'scan-ref', 'exit-code', 'ignore-unfixed', 'vuln-type', 'severity', 'format', 'template', 'output', 'skip-dirs', 'skip-files', 'cache-dir', 'timeout', 'ignore-policy', 'hide-progress', 'list-all-pkgs', 'scanners', 'trivyignores', 'artifact-type', 'github-pat', 'trivy-config', 'tf-vars', 'limit-severities-for-sarif', 'docker-host']
docker-build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, docker/login-action@v2, docker/metadata-action@v4, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/