chore: prepare for v0.1.1 release #26
cigraingerci.yml
on: pull_request
Format check
15s
Rust lint
30s
Matrix: test
Annotations
3 errors and 20 warnings
|
Format check
Process completed with exit code 1.
|
|
Test (OTP 27 / Elixir 1.18)
Process completed with exit code 2.
|
|
Test (OTP 28 / Elixir 1.19)
Process completed with exit code 2.
|
|
Format check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/
|
|
Rust lint
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/
|
|
Test (OTP 27 / Elixir 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_correctness_peer_test.exs#L464
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L369
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L407
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L434
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L462
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L532
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
test/dux/distributed_join_routing_test.exs#L576
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 27 / Elixir 1.18):
lib/dux.ex#L722
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_correctness_peer_test.exs#L464
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L369
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L407
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L434
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L462
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L532
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
test/dux/distributed_join_routing_test.exs#L576
Nested modules could be aliased at the top of the invoking module.
|
|
Test (OTP 28 / Elixir 1.19):
lib/dux.ex#L722
Nested modules could be aliased at the top of the invoking module.
|