Bump github.com/quic-go/quic-go from 0.53.0 to 0.59.1 #97
dependabot[bot]Annotations
47 errors, 6 warnings, and 2 notices
|
build (1.22, ubuntu-latest)
Process completed with exit code 1.
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L535
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L494
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L453
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L367
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L316
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L256
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L183
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L135
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest):
httputil/http_test.go#L76
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest)
The strategy configuration was canceled because "build._1_22_ubuntu-latest" failed
|
|
build (1.21, ubuntu-latest)
The operation was canceled.
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L535
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L494
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L453
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L367
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L316
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L256
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L183
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L135
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, ubuntu-latest):
httputil/http_test.go#L76
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, windows-latest)
The strategy configuration was canceled because "build._1_22_ubuntu-latest" failed
|
|
build (1.22, windows-latest)
The operation was canceled.
|
|
build (1.21, windows-latest)
The strategy configuration was canceled because "build._1_22_ubuntu-latest" failed
|
|
build (1.21, windows-latest)
The operation was canceled.
|
|
build (1.21, macos-latest)
The strategy configuration was canceled because "build._1_22_ubuntu-latest" failed
|
|
build (1.21, macos-latest)
The operation was canceled.
|
|
build (1.21, macos-latest):
httputil/http_test.go#L535
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L494
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L453
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L367
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L316
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L256
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L183
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L135
non-constant format string in call to fmt.Fprintf
|
|
build (1.21, macos-latest):
httputil/http_test.go#L76
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest)
The strategy configuration was canceled because "build._1_22_ubuntu-latest" failed
|
|
build (1.22, macos-latest)
The operation was canceled.
|
|
build (1.22, macos-latest):
httputil/http_test.go#L535
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L494
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L453
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L367
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L316
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L256
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L183
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L135
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, macos-latest):
httputil/http_test.go#L76
non-constant format string in call to fmt.Fprintf
|
|
build (1.22, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.21, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.22, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.21, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.21, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.22, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build (1.22, windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
build (1.21, windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|