Skip to content

add flag for --include-system-workers for ListWorker API #1791

add flag for --include-system-workers for ListWorker API

add flag for --include-system-workers for ListWorker API #1791

Triggered via pull request May 1, 2026 20:15
Status Failure
Total duration 3m 30s
Artifacts 5

ci.yaml

on: pull_request
Validate Server Version
16s
Validate Server Version
Matrix: build-test
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 6 warnings
build-test (ubuntu-arm)
Process completed with exit code 1.
build-test (ubuntu-arm): internal/temporalcli/commands.worker.go#L144
unknown field IncludeSystemWorkers in struct literal of type workflowservice.ListWorkersRequest
build-test (macos-latest)
Process completed with exit code 1.
build-test (macos-latest): internal/temporalcli/commands.worker.go#L144
unknown field IncludeSystemWorkers in struct literal of type workflowservice.ListWorkersRequest
build-test (macos-15-intel)
Process completed with exit code 1.
build-test (macos-15-intel): internal/temporalcli/commands.worker.go#L144
unknown field IncludeSystemWorkers in struct literal of type workflowservice.ListWorkersRequest
build-test (windows-latest)
Process completed with exit code 1.
build-test (windows-latest): internal/temporalcli/commands.worker.go#L144
unknown field IncludeSystemWorkers in struct literal of type workflowservice.ListWorkersRequest
build-test (ubuntu-latest)
Process completed with exit code 1.
build-test (ubuntu-latest): internal/temporalcli/commands.worker.go#L144
unknown field IncludeSystemWorkers in struct literal of type workflowservice.ListWorkersRequest
Validate Server Version
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-go@v5. 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/
build-test (ubuntu-arm)
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-go@v5, actions/upload-artifact@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/
build-test (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@v4, actions/setup-go@v5, actions/upload-artifact@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/
build-test (macos-15-intel)
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-go@v5, actions/upload-artifact@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/
build-test (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@v4, actions/setup-go@v5, actions/upload-artifact@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/
build-test (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@v4, actions/setup-go@v5, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
junit-xml--25231259088--1--macos-15-intel
1.66 KB
sha256:b91132ad404cf2ec21bb996fbc91e116edf030c944ba78c8160bd2934a09cd3a
junit-xml--25231259088--1--macos-latest
1.69 KB
sha256:886dbd7653527d0315bfcea6d4d5a687de3ccd33a3b1775e233415c762d42afa
junit-xml--25231259088--1--ubuntu-arm
1.66 KB
sha256:513e836627e9a0e8287ba0a673b2cac006167d51721c8916d457f7d337a9872c
junit-xml--25231259088--1--ubuntu-latest
1.69 KB
sha256:7a25aae16238c953bf3aabdcc5207784978124a5010fa368935adba3e24f44d1
junit-xml--25231259088--1--windows-latest
1.77 KB
sha256:a9e56a1d1c0d020fc18faac8ea641b16fe545d1792f870d5e65cbd506364a0e8