chore(main): release 0.14.2 (#546) #123
jokertturelease-please.yml
on: push
build-and-test
/
lint
1m 31s
build-and-test
/
check-objc-formatting
20s
build-and-test
/
check-java-and-kotlin-formatting
15s
build-and-test
/
test
2s
build-and-test
/
build-library
1m 25s
build-and-test
/
build-android
1m 29s
build-and-test
/
build-ios
2m 3s
publish
/
...
/
lint
30s
publish
/
...
/
check-objc-formatting
10s
publish
/
...
/
check-java-and-kotlin-formatting
17s
publish
/
...
/
test
3s
publish
/
...
/
build-library
25s
publish
/
...
/
build-android
19s
publish
/
...
/
build-ios
1m 8s
publish
/
publish
1m 7s
Annotations
34 warnings
|
build-and-test / check-java-and-kotlin-formatting
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@v3. 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-and-test / check-objc-formatting
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 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-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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-and-test / lint
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@v4, actions/setup-node@v3. 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-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
build-and-test / build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
build-and-test / build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
release-please
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: googleapis/release-please-action@v4. 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/
|
|
publish / build-and-test / check-objc-formatting
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 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/
|
|
publish / build-and-test / check-java-and-kotlin-formatting
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@v3. 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/
|
|
publish / build-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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/
|
|
publish / build-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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/
|
|
publish / build-and-test / lint
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@v4, actions/setup-node@v3. 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/
|
|
publish / build-and-test / 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@v3, actions/checkout@v4, actions/setup-node@v3. 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/
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
publish / build-and-test / build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
publish / build-and-test / build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
publish / build-and-test / build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
publish / publish
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-node@v4. 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/
|