Fix recommending a tier on the upgrade page #7879
You are viewing an older attempt in the history of this workflow run.
View latest attempt.
RobertJoonaselixir.yml
on: pull_request
Static checks (format, credo, dialyzer)
2m 15s
Matrix: build
Annotations
4 errors and 10 warnings
|
Build and test (test, postgres:16)
The job was canceled because "test_postgres_15_0" failed.
|
|
Build and test (test, postgres:16)
The operation was canceled.
|
|
Build and test (test, postgres:16, experimental_reduced_joins)
The job was canceled because "test_postgres_15_0" failed.
|
|
Build and test (test, postgres:16, experimental_reduced_joins)
The operation was canceled.
|
|
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
|
|
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
|
|
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
|
|
Static checks (format, credo, dialyzer)
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)
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)
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
|