Skip to content

Commit

Permalink
Test on Elixir 1.18 and NATS 2.10.24 (#188)
Browse files Browse the repository at this point in the history
  • Loading branch information
davydog187 authored Jan 9, 2025
1 parent 2224505 commit 813343d
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
8 changes: 6 additions & 2 deletions .github/workflows/CI.yml
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,15 @@ jobs:

- otp: "26"
elixir: "1.16"
nats: "2.10.14"
nats: "2.10.24"

- otp: "27"
elixir: "1.17"
nats: "2.10.14"
nats: "2.10.24"

- otp: "27"
elixir: "1.18"
nats: "2.10.24"

- otp: "27"
elixir: "main"
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ As of this commit my 2018 MacBook pro shows.

Before running the tests make sure you have a locally running copy of `nats-server` ([installation instructions](https://docs.nats.io/running-a-nats-service/introduction/installation)). By default, tests are run with no authentication. Make sure your NATS configuration contains no users, or has an account with [no_auth_user](https://docs.nats.io/running-a-nats-service/configuration/securing_nats/accounts#no-auth-user) explicitly enabled.

We currently use version `2.6.6` in CI, but anything higher than `2.2.0` should be fine.
We currently use version `2.10.24` in CI, but anything higher than `2.2.0` should be fine.
Versions from `0.9.6` up to `2.2.0` should work fine for everything except header support.
Make sure to enable jetstream with the `nats-server -js` argument and you might also want to enable debug and verbose logging if you're trying to understand the messages being sent to/from nats (ie `nats-server -js -D -V`).
The typical `mix test` will run all the basic unit tests.
Expand Down

0 comments on commit 813343d

Please sign in to comment.