Conversation
01f4e28 to
092dd2a
Compare
Pull Request Test Coverage Report for Build 092dd2a0a49f3098f29a423b998dea1ecf48e1f6-PR-82Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
19a8320 to
b6e6071
Compare
Got stuck with these issues! |
|
Ah I think |
|
I think it is ready now 😄 |
the-mikedavis
left a comment
There was a problem hiding this comment.
Looks like this just needs a run of the formatter too to pass CI
a282de2 to
b319e08
Compare
| description: description() | ||
| description: description(), | ||
| dialyzer: [ | ||
| plt_add_apps: [:jason], |
| elixir 1.14.5-otp-26 | ||
| erlang 26.0 |
There was a problem hiding this comment.
Adding this to the CI and using it locally is ok but we should also test against earlier Elixir versions as far back as 1.9
eb9f5e1 to
94b739a
Compare
905c237 to
7ea4094
Compare
| otp-version: ${{ matrix.beam.otp }} | ||
| elixir-version: ${{ matrix.beam.elixir }} | ||
| version-file: .tool-versions | ||
| version-type: strict | ||
|
|
There was a problem hiding this comment.
The compatibility workflow should check a range of old/new Elixir and Erlang/OTP versions rather than use the main .tool-versions. Removing credo and updating to the new actions v3 versions looks good though
There was a problem hiding this comment.
Right, my understanding is that it is valuable to check against a range of Event Store DB versions, but since Elixir 1.10, there is not much value in adding such a matrix IMO.
Being said, sure I can add it back
No description provided.