Skip to content

Bump python-dotenv from 1.0.0 to 1.2.2 in /api-server #141

Bump python-dotenv from 1.0.0 to 1.2.2 in /api-server

Bump python-dotenv from 1.0.0 to 1.2.2 in /api-server #141

Triggered via pull request April 21, 2026 18:25
Status Failure
Total duration 48s
Artifacts

ci.yml

on: pull_request
Matrix: Lint and Test
Security Scan
42s
Security Scan
Build and Integration Test
0s
Build and Integration Test
Build Production Images
0s
Build Production Images
Performance Testing
0s
Performance Testing
Create Release
0s
Create Release
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 4 warnings
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+003F '?'
Lint and Test (proxy-egress)
illegal character U+003F '?'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-egress)
illegal character U+005C '\'
Lint and Test (proxy-ingress)
The strategy configuration was canceled because "lint-and-test.proxy-egress" failed
Lint and Test (proxy-ingress)
Process completed with exit code 1.
Lint and Test (proxy-ingress)
package marchproxy-ingress/internal/tls is not in std (/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.7.linux-amd64/src/marchproxy-ingress/internal/tls)
Lint and Test (proxy-ingress)
package marchproxy-ingress/internal/ebpf is not in std (/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.24.7.linux-amd64/src/marchproxy-ingress/internal/ebpf)
Lint and Test (manager)
The strategy configuration was canceled because "lint-and-test.proxy-egress" failed
Lint and Test (manager)
Process completed with exit code 1.
Security Scan
Path does not exist: proxy-ingress/gosec-results-ingress.sarif
Security Scan
Path does not exist: proxy-egress/gosec-results-egress.sarif
Security Scan
Process completed with exit code 1.
Security Scan
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Lint and Test (proxy-egress)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Lint and Test (proxy-ingress)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Lint and Test (manager)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Security Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, github/codeql-action/upload-sarif@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/