Elixir package CI #916
tombruijnci.yaml
on: schedule
validate-changesets
/
Validate changesets
6s
lint_git
0s
lint_format
12s
lint_credo
1m 14s
lint_compile
1m 17s
lint_dialyzer
2m 57s
test_diagnose
1m 22s
test_no_nif
1m 4s
Matrix: test
Annotations
150 warnings
|
validate-changesets / Validate changesets
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 16th, 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/
|
|
lint_format
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 16th, 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/
|
|
test (1.16, 26)
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 16th, 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/
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.16, 26)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.16, 26)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.16, 26)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test (1.14, 25)
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 16th, 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/
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.14, 25)
Map.intersect/2 is undefined or private
|
|
test (1.14, 25)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.14, 25)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.14, 25)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test_no_nif
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 16th, 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/
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test_no_nif
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (1.19.5, 26)
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 16th, 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/
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 26)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (main, 28)
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 16th, 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/
|
|
test (main, 28)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (main, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (main, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (main, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (main, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (main, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (main, 28)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (main, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (main, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (main, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (1.15, 26)
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 16th, 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/
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.15, 26)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.15, 26)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.15, 26)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test (latest, 28)
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 16th, 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/
|
|
test (latest, 28)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (latest, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (latest, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (latest, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (latest, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (latest, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (latest, 28)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (latest, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (latest, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (latest, 28)
"xref: [exclude: ...]" in your mix.exs file is deprecated, instead use: "elixirc_options: [no_warn_undefined: ...]"
|
|
test (1.13, 24)
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 16th, 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/
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.13, 24)
Map.intersect/2 is undefined or private
|
|
test (1.13, 24)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.13, 24)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.13, 24)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test (1.12, 24)
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 16th, 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/
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.12, 24)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.12, 24)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.12, 24)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test (1.19.5, 27)
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 16th, 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/
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 27)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (1.19.5, 28)
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 16th, 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/
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.19.5, 28)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
test (1.17, 27)
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 16th, 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/
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
erlang:get_stacktrace/0 is removed; use the new try/catch syntax for retrieving the stack backtrace
|
|
test (1.17, 27)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.17, 27)
ssl:cipher_suites/0 is removed; use cipher_suites/2,3 instead
|
|
test (1.17, 27)
ssl:ssl_accept/2 is removed; use ssl_handshake/1,2,3 instead
|
|
test (1.18, 27)
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 16th, 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/
|
|
test (1.18, 27)
Supervisor.start_child/2 with a list of args is deprecated, please use DynamicSupervisor instead
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
appsignal: Deprecation warning: The `skip_session_data` config option is deprecated. Please use `send_session_data` instead.
|
|
test (1.18, 27)
:simple_one_for_one strategy is deprecated, please use DynamicSupervisor instead
|
|
lint_credo
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 16th, 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/
|
|
lint_compile
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 16th, 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/
|
|
test_diagnose
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 16th, 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/
|
|
lint_dialyzer
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 16th, 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/
|
|
lint_dialyzer
Failed to restore:
|