Skip to content

feat: add web support via CSS transitions #40

feat: add web support via CSS transitions

feat: add web support via CSS transitions #40

Triggered via pull request March 15, 2026 07:03
Status Failure
Total duration 8m 46s
Artifacts –

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 16 warnings
build-android
Process completed with exit code 1.
build-android
react-native-ease-example#build:android: command (/home/runner/work/react-native-ease/react-native-ease/example) /tmp/xfs-2cbb395c/yarn run build:android exited (1)
build-library
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
build-library
Cache save failed.
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
build-android
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
build-android
Cache save failed.
build-ios
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, maxim-lobanov/setup-xcode@60606e260d2fc5762a71e64e74b2174e8ea3c8bd. 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/
build-ios: example/ios/Pods/Headers/Private/RNWorklets/worklets/WorkletRuntime/WorkletRuntime.h#L142
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Private/RNWorklets/worklets/WorkletRuntime/WorkletRuntime.h#L156
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Private/RNWorklets/worklets/WorkletRuntime/WorkletRuntime.h#L154
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Private/RNWorklets/worklets/WorkletRuntime/WorkletRuntime.h#L151
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Private/RNWorklets/worklets/WorkletRuntime/WorkletRuntime.h#L148
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Public/React-Fabric/react/renderer/mounting/ShadowViewMutation.h#L74
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Public/React-Fabric/react/renderer/mounting/ShadowViewMutation.h#L60
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/ios/Pods/Headers/Public/React-Fabric/react/renderer/mounting/ShadowViewMutation.h#L46
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
build-ios: example/node_modules/expo-modules-core/ios/JSI/EXJavaScriptRuntime.mm#L61
conflicting parameter types in implementation of 'initWithRuntime:callInvoker:': 'shared_ptr<react::CallInvoker>' vs 'shared_ptr<react::RuntimeSchedulerCallInvoker>' [-Wmismatched-parameter-types]
build-ios: example/node_modules/expo-modules-core/ios/JSI/EXJavaScriptRuntime.mm#L61
conflicting parameter types in implementation of 'initWithRuntime:callInvoker:': 'shared_ptr<react::CallInvoker>' vs 'shared_ptr<react::RuntimeSchedulerCallInvoker>' [-Wmismatched-parameter-types]