Merge pull request #47 from lanodan/fix/elixir-1.14 #9
Annotations
20 errors and 19 warnings
Build and test (1.7.4, 21.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.10.3, 22.3.4)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.9.4, 22.3.4)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.11.3, 22.3.4)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Credo
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.8.2, 22.3.4)
The job was canceled because "_1_7_4_21_2" failed.
|
Build and test (1.8.2, 22.3.4)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.11.3, 21.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.10.3, 21.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.9.4, 21.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.7.4, 23.0.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.8.2, 23.0.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.8.2, 21.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.7.4, 22.3.4)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.9.4, 20.3.8)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.9.4, 23.0.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.10.3, 23.0.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.7.4, 20.3.8)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.8.2, 20.3.8)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.11.3, 23.0.2)
The process '/home/runner/work/_temp/.setup-elixir/elixir/bin/mix' failed with exit code 127
|
Build and test (1.7.4, 21.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.10.3, 22.3.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.9.4, 22.3.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.11.3, 22.3.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Credo
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.8.2, 22.3.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.11.3, 21.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.10.3, 21.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.9.4, 21.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.7.4, 23.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.8.2, 23.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.8.2, 21.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.7.4, 22.3.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.9.4, 20.3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.9.4, 23.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.10.3, 23.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.7.4, 20.3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.8.2, 20.3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build and test (1.11.3, 23.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-elixir@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|