Skip to content

Support multi-valued fields in rewrite and advancedrewrite plugins #7750

Support multi-valued fields in rewrite and advancedrewrite plugins

Support multi-valued fields in rewrite and advancedrewrite plugins #7750

Triggered via pull request April 10, 2026 09:41
Status Cancelled
Total duration 2m 40s
Artifacts

ci.yaml

on: pull_request
Matrix: Run tests
Upload coverage report
Upload coverage report
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 8 warnings
Run tests (windows-latest, 3.10)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (windows-latest, 3.10)
The operation was canceled.
Run tests (ubuntu-latest, 3.12)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (ubuntu-latest, 3.12)
The operation was canceled.
Run tests (windows-latest, 3.13)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (windows-latest, 3.13)
The operation was canceled.
Run tests (windows-latest, 3.11)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (windows-latest, 3.11)
The operation was canceled.
Run tests (windows-latest, 3.12)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (windows-latest, 3.12)
The operation was canceled.
Run tests (ubuntu-latest, 3.10)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (ubuntu-latest, 3.10)
The operation was canceled.
Run tests (ubuntu-latest, 3.11)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (ubuntu-latest, 3.11)
The operation was canceled.
Run tests (ubuntu-latest, 3.13)
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (ubuntu-latest, 3.13)
The operation was canceled.
Test
Canceling since a higher priority waiting request for Test-refs/pull/6518/merge exists
Run tests (windows-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (windows-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (windows-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (ubuntu-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (ubuntu-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/
Run tests (ubuntu-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BrandonLWhite/pipx-install-action@v1.0.3, liskin/gh-problem-matcher-wrap@v3, tj-actions/changed-files@v46. 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/