feat: Use the proxy v2 engine but keep CLI flags unchanged. #8082
hessjcgtests.yaml
on: pull_request
Matrix: integration tests
Matrix: unit tests
Annotations
32 errors and 45 warnings
|
unit tests (1.23)
Process completed with exit code 1.
|
|
unit tests (1.23)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.23)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.23):
cmd/cloud_sql_proxy/cloud_sql_proxy.go#L55
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
Process completed with exit code 1.
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (ubuntu-latest):
cmd/cloud_sql_proxy/cloud_sql_proxy.go#L55
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.24)
Process completed with exit code 1.
|
|
unit tests (1.24)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.24)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.24):
cmd/cloud_sql_proxy/cloud_sql_proxy.go#L55
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
Process completed with exit code 1.
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (macos-latest):
cmd/cloud_sql_proxy/cloud_sql_proxy.go#L55
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
Process completed with exit code 1.
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest)
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
integration tests (windows-latest):
cmd/cloud_sql_proxy/cloud_sql_proxy.go#L55
github.com/GoogleCloudPlatform/cloud-sql-proxy/v2@v2.21.2: replacement directory ../proxy-v2 does not exist
|
|
unit tests (1.23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, google-github-actions/auth@v0.8.0. 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/
|
|
unit tests (1.23)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
unit tests (1.23)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, google-github-actions/auth@v0.8.0, google-github-actions/get-secretmanager-secrets@v0.5.0. 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/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
unit tests (1.24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, google-github-actions/auth@v0.8.0. 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/
|
|
unit tests (1.24)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
unit tests (1.24)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, google-github-actions/auth@v0.8.0, google-github-actions/get-secretmanager-secrets@v0.5.0. 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/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (macos-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, google-github-actions/auth@v0.8.0, google-github-actions/get-secretmanager-secrets@v0.5.0. 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/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
integration tests (windows-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|