Skip to content

feat(3091): Store user metadata in ios native storage for notifications #3872

feat(3091): Store user metadata in ios native storage for notifications

feat(3091): Store user metadata in ios native storage for notifications #3872

Triggered via pull request March 13, 2026 18:07
Status Success
Total duration 1h 20m 5s
Artifacts

e2e-crossplatform.yml

on: pull_request
Matrix: linux-back-compat / linux
Matrix: linux-qss / linux
Matrix: linux / linux
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
linux-back-compat / linux (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, Saionaro/extract-package-version@fdb5b74adc1278ddb777dfed4c988b9d098bb48d. 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/
linux-qss / linux (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, docker/setup-docker-action@v4, nick-fields/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4, Saionaro/extract-package-version@fdb5b74adc1278ddb777dfed4c988b9d098bb48d. 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/
mac / mac
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/setup-python@v5, nick-fields/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
linux / linux (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, nick-fields/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4, nick-fields/retry@v2, Saionaro/extract-package-version@fdb5b74adc1278ddb777dfed4c988b9d098bb48d. 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/
linux / linux (ubuntu-22.04)
Attempt 2 failed. Reason: Timeout of 1500000ms hit
linux / linux (ubuntu-22.04)
Attempt 1 failed. Reason: Timeout of 1500000ms hit
linux / linux (ubuntu-22.04)
Attempt 1 failed. Reason: Child_process exited with error code 1