chore(deps): update module go.mongodb.org/mongo-driver to v2 #1163
renovate[bot]pr-build.yaml
on: pull_request
Matrix: e2e-tests
test-chart
0s
test-success
Annotations
29 errors and 8 warnings
|
build
Process completed with exit code 2.
|
|
build:
internal/database/mongodb.go#L12
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
build:
internal/database/mongodb.go#L11
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
build:
internal/database/mongodb.go#L10
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
build:
internal/database/mongodb.go#L9
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
build:
internal/database/mongodb.go#L8
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.32)
Process completed with exit code 2.
|
|
test (1.32):
internal/database/mongodb.go#L12
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.32):
internal/database/mongodb.go#L11
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.32):
internal/database/mongodb.go#L10
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.32):
internal/database/mongodb.go#L9
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.32):
internal/database/mongodb.go#L8
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
fmt
Process completed with exit code 2.
|
|
fmt:
internal/database/mongodb.go#L12
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
fmt:
internal/database/mongodb.go#L11
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
fmt:
internal/database/mongodb.go#L10
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
fmt:
internal/database/mongodb.go#L9
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
fmt:
internal/database/mongodb.go#L8
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.33)
The strategy configuration was canceled because "test._1_32" failed
|
|
test (1.33)
The operation was canceled.
|
|
test (1.31)
The strategy configuration was canceled because "test._1_32" failed
|
|
test (1.31)
The operation was canceled.
|
|
test (1.34)
The strategy configuration was canceled because "test._1_32" failed
|
|
test (1.34)
The operation was canceled.
|
|
test (1.34):
internal/database/mongodb.go#L12
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.34):
internal/database/mongodb.go#L11
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.34):
internal/database/mongodb.go#L10
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.34):
internal/database/mongodb.go#L9
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
test (1.34):
internal/database/mongodb.go#L8
go.mongodb.org/mongo-driver/v2@v2.6.0: missing go.sum entry for go.mod file; to add it:
|
|
lint-chart
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065, azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. 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-chart
No file matched to [/home/runner/work/db-controller/db-controller/**/*requirements*.txt,/home/runner/work/db-controller/db-controller/**/*requirements*.in,/home/runner/work/db-controller/db-controller/**/*constraints*.txt,/home/runner/work/db-controller/db-controller/**/*constraints*.in,/home/runner/work/db-controller/db-controller/**/pyproject.toml,/home/runner/work/db-controller/db-controller/**/uv.lock,/home/runner/work/db-controller/db-controller/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|
|
test (1.32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|
|
fmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|
|
test (1.33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|
|
test (1.31)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|
|
test (1.34)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. 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/
|