Skip to content

Releases: nats-io/stan.go

Release v0.10.4

11 Jan 23:12
d2049c1
Compare
Choose a tag to compare

Changelog

Updated

  • Dependencies (#370)
    • github.com/nats-io/nats.go v1.16.0 -> v1.22.1
    • golang.org/x/crypto v0.0.0-20220722155217-630584e8d5aa -> v0.5.0

Complete Changes

v0.10.3...v0.10.4

Release v0.10.3

29 Jul 18:41
98ecfee
Compare
Choose a tag to compare

Changelog

Updated

  • NATS Go client dependency, from v0.13.0 to v0.16.0 (#367)

Fixed

Complete Changes

v0.10.2...v0.10.3

Release v0.10.2

17 Nov 19:47
366e4de
Compare
Choose a tag to compare

Changelog

Added/Changed

  • AllowCloseRetry option to be able to retry connection Close() on failure. In PR #360, a failed Close() would cause the underlying NATS connection to not be closed, which could have undesired behavior for users that did not check Close() status and would not call it again until success. Adding this new option restores original behavior by default, and forces users to use this option to change the behavior of connection Close(), with the understanding of the possible side effect (#361)

Complete Changes

v0.10.1...v0.10.2

Release v0.10.1

09 Nov 23:17
9937a12
Compare
Choose a tag to compare

Changelog

Fixed

  • Ability to retry a connection Close() or subscription Close() and Unsubscribe() if the protocol failed to be properly sent or received. Thanks to @mihai-tiriplica-f3 for the feedback (#360)

Complete Changes

v0.10.0...v0.10.1

Release v0.10.0

02 Aug 19:19
9a6e4f2
Compare
Choose a tag to compare

Changelog

The master branch was renamed to main. If you have a fork/clone of the repo, you may have to run this:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

Deprecated

  • The NatsConn() option is deprecated, the new option NatsOptions() should be used instead. Thanks to @Russiancold for the suggestion (#355)

Added

  • NatsOptions() option to configure the underlying NATS connection used by the Streaming connection. Thanks to @Russiancold for the suggestion (#355)

Complete Changes

v0.9.0...v0.10.0

Release v0.9.0

21 May 20:34
1f563ca
Compare
Choose a tag to compare

Changelog

Updated

  • NATS client dependency to v1.11.0 (#350)

Complete Changes

v0.8.3...v0.9.0

Release v0.8.3

26 Feb 01:12
910e9bc
Compare
Choose a tag to compare

Changelog

Fixed

  • Subscribe timeout should send a close request (#347)

Complete Changes

v0.8.2...v0.8.3

Release v0.8.2

11 Jan 20:44
cebf22c
Compare
Choose a tag to compare

Changelog

Updated

  • protobuf dependency (#342)

Complete Changes

v0.8.1...v0.8.2

Release v0.8.1

09 Jan 00:25
9c3dd6c
Compare
Choose a tag to compare

Changelog

Fixed

  • More fixes for protobuf's Unmarshal() (#340)

Complete Changes

v0.8.0...v0.8.1

Release v0.8.0

08 Jan 23:28
0fff1f5
Compare
Choose a tag to compare

Changelog

Added

  • Benchmark tool: ability to set a username/password and/or TLS certificates. Thanks to @lmtyler for the contribution (#318)
  • Note about reconnection in README. Thanks to @KidLinus for the recommendation (#323)
  • Note about MsgProto.Timestamp precision in protocol.proto. Thanks to @palsivertsen for the recommendation (#329)

Changed

  • Default pings settings will now be 5 second and 88 failures, which better matches to the default server heartbeat settings. The original 5sec and 3 failures were too small and would cause a client to consider the connection lost after a very short server downtime (#337)

Fixed

  • Do not panic on protobuf's Unmarshal() errors (#338)

Complete Changes

v0.7.0...v0.8.0