chore(deps): update dependency erlang to v28 #274
renovate[bot]astarte-libs-workflow.yml
on: pull_request
astarte_data_access
/
Cache warmup
16s
astarte_events
/
Cache warmup
14s
astarte_generators
/
Cache warmup
22s
astarte_rpc
/
Cache warmup
15s
astarte_data_access
/
Formatting
0s
astarte_data_access
/
Credo
0s
astarte_data_access
/
Dialyzer
0s
Matrix: astarte_data_access / Test
astarte_events
/
Formatting
0s
astarte_events
/
Credo
0s
astarte_events
/
Dialyzer
0s
Matrix: astarte_events / Test
astarte_generators
/
Formatting
0s
astarte_generators
/
Credo
0s
astarte_generators
/
Dialyzer
Matrix: astarte_generators / Test
astarte_rpc
/
Formatting
0s
astarte_rpc
/
Credo
0s
astarte_rpc
/
Dialyzer
0s
Matrix: astarte_rpc / Test
Annotations
4 errors and 4 warnings
|
astarte_data_access / Cache warmup
Process completed with exit code 1.
|
|
astarte_rpc / Cache warmup
Process completed with exit code 1.
|
|
astarte_events / Cache warmup
Process completed with exit code 1.
|
|
astarte_generators / Cache warmup
Process completed with exit code 1.
|
|
astarte_data_access / Cache warmup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, erlef/setup-beam@v1. 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/
|
|
astarte_rpc / Cache warmup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, erlef/setup-beam@v1. 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/
|
|
astarte_events / Cache warmup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, erlef/setup-beam@v1. 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/
|
|
astarte_generators / Cache warmup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, erlef/setup-beam@v1. 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/
|