Skip to content

Support string fields in input_changed?/3 (#428) #188

Support string fields in input_changed?/3 (#428)

Support string fields in input_changed?/3 (#428) #188

Triggered via push August 15, 2023 20:39
Status Failure
Total duration 28s
Artifacts

ci.yml

on: push
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Run tests (Elixir 1.14, OTP 25.3)
Process completed with exit code 1.
Run tests (Elixir 1.7, OTP 21.3)
The operation was canceled.
Run tests (Elixir 1.14, OTP 25.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (Elixir 1.7, OTP 21.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (Elixir 1.7, OTP 21.3)
System.stacktrace/0 outside of rescue/catch clauses is deprecated. If you want to support only Elixir v1.7+, you must access __STACKTRACE__ inside a rescue/catch. If you want to support earlier Elixir versions, move System.stacktrace/0 inside a rescue/catch
Run tests (Elixir 1.7, OTP 21.3)
MIME.valid?/1 is deprecated. Use MIME.extensions(type) != [] instead