Skip to content

Fix sender header insertion with respect to membership changes #1022

Fix sender header insertion with respect to membership changes

Fix sender header insertion with respect to membership changes #1022

Triggered via pull request January 7, 2024 08:35
Status Failure
Total duration 1m 51s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test.yml

on: pull_request
Matrix: build

Annotations

4 errors and 4 warnings
build (29.1)
Process completed with exit code 3.
build (27.2)
Process completed with exit code 4.
build (snapshot)
Process completed with exit code 3.
build (28.2)
Process completed with exit code 4.
build (29.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (27.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (snapshot)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (28.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/