From 196c238a7974634009397eb7e96eef05c4b7e6cb Mon Sep 17 00:00:00 2001 From: Michael Ries Date: Mon, 24 Jun 2024 11:45:49 -0700 Subject: [PATCH] release 1.8.4 --- CHANGELOG.md | 2 ++ README.md | 1 + mix.exs | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a56e17d..3cdc4ca 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,8 @@ * Add ability to list KV buckets https://github.com/nats-io/nats.ex/pull/152 * Improve CI Reliability https://github.com/nats-io/nats.ex/pull/154 * Bugfix to treat no streams as an empty list rather than a null https://github.com/nats-io/nats.ex/pull/155 +* Added supported for `allow_direct` and `mirror_direct` attributes of streams https://github.com/nats-io/nats.ex/pull/161 +* Added support for `discard_new_per_subject` attribute of streams https://github.com/nats-io/nats.ex/pull/163 ## 1.7 diff --git a/README.md b/README.md index 94675d8..40adb7b 100644 --- a/README.md +++ b/README.md @@ -134,6 +134,7 @@ Before running the tests make sure you have a locally running copy of `nats-serv We currently use version `2.6.6` 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. You can also run the `multi_server` set of tests that test connectivity to different diff --git a/mix.exs b/mix.exs index fbb5a5e..4215220 100644 --- a/mix.exs +++ b/mix.exs @@ -2,7 +2,7 @@ defmodule Gnat.Mixfile do use Mix.Project @source_url "https://github.com/nats-io/nats.ex" - @version "1.8.3" + @version "1.8.4" def project do [