Releases: nats-io/stan.go
Releases · nats-io/stan.go
Release v0.10.4
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
Release v0.10.3
Changelog
Updated
- NATS Go client dependency, from v0.13.0 to v0.16.0 (#367)
Fixed
- Memory leak for failed Streaming subscriptions. Thanks to @oncicaradupopovici for the contribution (#366)
Complete Changes
Release v0.10.2
Changelog
Added/Changed
AllowCloseRetry
option to be able to retry connectionClose()
on failure. In PR #360, a failedClose()
would cause the underlying NATS connection to not be closed, which could have undesired behavior for users that did not checkClose()
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 connectionClose()
, with the understanding of the possible side effect (#361)
Complete Changes
Release v0.10.1
Changelog
Fixed
- Ability to retry a connection
Close()
or subscriptionClose()
andUnsubscribe()
if the protocol failed to be properly sent or received. Thanks to @mihai-tiriplica-f3 for the feedback (#360)
Complete Changes
Release v0.10.0
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 optionNatsOptions()
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
Release v0.9.0
Release v0.8.3
Release v0.8.2
Release v0.8.1
Release v0.8.0
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 inprotocol.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)