Skip to content

0.2.4 - Bridge callback fixes, post-build pod install, CI workflows #3

0.2.4 - Bridge callback fixes, post-build pod install, CI workflows

0.2.4 - Bridge callback fixes, post-build pod install, CI workflows #3

Triggered via pull request May 29, 2026 09:29
@ianrumacianrumac
synchronize #1
ir/fixes+ci
Status Success
Total duration 1m 39s
Artifacts

native.yml

on: pull_request
iOS bridge (SPM)
1m 35s
iOS bridge (SPM)
Android lib (Gradle)
1m 23s
Android lib (Gradle)
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Android lib (Gradle)
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-java@v4, android-actions/setup-android@v3, gradle/actions/setup-gradle@v3. 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/
Android lib (Gradle)
Restore Gradle distribution 8.7 failed: Error: Cache service responded with 400
Android lib (Gradle)
Failed to restore gradle-home-v1|Linux|android[76ed096149854ea0bcdde898e9083154]-f0079510309e0487c2f9ad140a59e7c8fe10a652: Error: Cache service responded with 400
iOS bridge (SPM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/