Skip to content
Continuous Releases

feat: add ability to use custom wd request agent #84

Sign in to view logs

feat: add ability to use custom wd request agent

feat: add ability to use custom wd request agent #84

Triggered via pull request April 14, 2026 22:43
@KuznetsovRomanKuznetsovRoman
synchronize #40
TESTPLANE-944.accept_custom_agent
Status Failure
Total duration 1m 4s
Artifacts –

cr.yml

on: pull_request
build
1m 0s
build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
build
Process completed with exit code 1.
build
Property '_libRequest' in type 'WebRequest' is not assignable to the same property in base type 'WebDriverRequest'.
build
Conversion of type 'Response<unknown>' to type 'RequestLibResponse<unknown>' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
build
Property 'customWdRequestAgent' does not exist on type 'RequestOptions'.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-node@v4, pnpm/action-setup@v4. 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/