Bump the go-dependencies group across 2 directories with 6 updates #1242
dependabot[bot]ci.yaml
on: pull_request
Go lint
56s
Release
1m 56s
Matrix: Go build and test
Matrix: JS Build and Test
Matrix: JS Lint
Annotations
15 errors and 10 warnings
|
Go lint
Process completed with exit code 2.
|
|
Go lint
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)) (typecheck)
|
|
Go lint:
riverproui/internal/prohandler/pro_handler_api_endpoints.go#L20
could not import riverqueue.com/riverpro (-: # riverqueue.com/riverpro
|
|
Go build and test (1.25, 17)
Process completed with exit code 2.
|
|
Go build and test (1.25, 17)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
Go build and test (1.25, 18)
Process completed with exit code 2.
|
|
Go build and test (1.25, 18)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
Go build and test (1.25, 16)
Process completed with exit code 2.
|
|
Go build and test (1.25, 16)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
Go build and test (1.26, 17)
Process completed with exit code 2.
|
|
Go build and test (1.26, 17)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
Go build and test (1.26, 16)
Process completed with exit code 2.
|
|
Go build and test (1.26, 16)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
Go build and test (1.26, 18)
Process completed with exit code 2.
|
|
Go build and test (1.26, 18)
cannot use pilot (variable of type *propilot.ProPilot) as riverpilot.Pilot value in argument to proDriver.ProConfigInit: *propilot.ProPilot does not implement riverpilot.Pilot (missing method JobCancel)
|
|
JS Lint (22.18.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
JS Build and Test (22.18.0)
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-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go lint
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.25, 17)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.25, 18)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.25, 16)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.26, 17)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.26, 16)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Go build and test (1.26, 18)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Release
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-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|