Skip to content

Releases: davenverse/rediculous

v0.2.0-M2

17 Nov 06:13
Compare
Choose a tag to compare
v0.2.0-M2 Pre-release
Pre-release
  • Add Publish command to RedisPubsub (This isn't special, its just a normal call to publish, but a pubsub without a publish method is weird)
  • Add publish to RedisCommands

v0.2.0-M1

17 Nov 05:06
Compare
Choose a tag to compare
v0.2.0-M1 Pre-release
Pre-release
  • Adds RedisPubSub Implementation
  • Lowers Constrain from Async to Concurrent for most operations

v0.1.1

23 Sep 21:42
d798008
Compare
Choose a tag to compare
  • Fixes An Error In Connection Acquisition

v0.1.0

13 Aug 03:33
74c6989
Compare
Choose a tag to compare
  • ScalaJS Implementation
  • Cats-Effect 3
  • Scala 2.12, 2.13, 3
  • Added RedisIO for direct use rather than Redis[IO, *] which has issues on Scala 3

v0.1.0-M1

30 Jul 20:21
7d7bf7f
Compare
Choose a tag to compare
v0.1.0-M1 Pre-release
Pre-release
  • Cats-Effect 3
  • ScalaJS Support Implementation
  • Scala 3 Support
  • On a hash version of fs2 for scalaJS until that is released. Should be binary compatible for jvm, feel free to explicitly set it.
  • Dropped 2.12 Support - Adding Scala 3 made 2.12 no longer infer correctly. PRs' accepted if this is wanted.

v0.0.12

13 Jan 23:42
d797ff3
Compare
Choose a tag to compare
  • Scala 3 Releases: 3.0.0-M2, 3.0.0-M3

v0.0.11

12 Jan 20:20
e9c66b3
Compare
Choose a tag to compare
  • Use Entire Cluster to Refresh Topology, if any succeeed use that. More likely to resolve more quickly with this approach.

v0.0.10

11 Jan 21:51
ac104d6
Compare
Choose a tag to compare
  • Fixed Release Process Hopefully

v0.0.9

11 Jan 21:41
8ad9bd7
Compare
Choose a tag to compare
v0.0.9 Pre-release
Pre-release
  • Fix Return Type of set

v0.0.8

08 Sep 20:32
c59eccd
Compare
Choose a tag to compare
v0.0.8 Pre-release
Pre-release
  • Fix SETEX Command
  • Limit Cluster Topology Refresh
  • Add Configuration Options for Cluster Refresh
    • CacheLifetime - how long it should not be refreshed again
    • UseDynamicRefresh - whether it should use a random node in the topology to refresh or the static initially communicated with
  • Refresh Topology on Cluster Errors. This fixes a possible error where if a node is removed from the cluster we may never receive a MOVED for these and try to connect to a server we cannot connect to but we don't go see who we should be communicating with. So when we receive an error in our normal communication to the remote we make sure we know what the topology is before returning that error to the user.