Skip to content
Elixir CI

Bump req from 0.5.0 to 0.5.6 #8968

Sign in to view logs

Bump req from 0.5.0 to 0.5.6

Bump req from 0.5.0 to 0.5.6 #8968

Triggered via pull request September 6, 2024 08:07
@zoldarzoldar
synchronize #4537
dependabot/hex/req-0.5.6
Status Success
Total duration 4m 27s
Artifacts –

elixir.yml

on: pull_request
Static checks (format, credo, dialyzer)
1m 58s
Static checks (format, credo, dialyzer)
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
Static checks (format, credo, dialyzer)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it