v3.0.2

What's Changed

• support nil logger by @navidemad in #39

New Contributors

• @navidemad made their first contribution in #39

Full Changelog: v3.0.1...v3.0.2

v3.0.1

What's Changed

• Remove updated_at column by @brunoprietog in #27
• Align indentation with the Omakase style by @brunoprietog in #28
• Remove frozen_string_literal comment from cable_schema install template by @brunoprietog in #29
• Fix installing Solid Queue by @morgoth in #31
• Attempt to clarify the note on postgres support by @jpcamara in #32
• Add single database configuration instructions by @jimmypoulsen in #37

New Contributors

• @brunoprietog made their first contribution in #27
• @jpcamara made their first contribution in #32
• @jimmypoulsen made their first contribution in #37

Full Changelog: v3.0.0...v3.0.1

v3.0.0

What's Changed

• Hash channel name to have a more compact index by @npezza93 in #14
• Add trilogy and pg to test suite by @npezza93 in #16
• Enhance trimming to be more performant by @npezza93 in #15
• Add rubocop omakase gem by @npezza93 in #18
• Rely on rails components instead of blanket rails by @npezza93 in #21
• Fix default polling silencing by @morgoth in #23
• Set timeout on CI by @morgoth in #22
• Add benchmarks and tune up the benchmark app by @npezza93 in #24

Breaking Changes

If you are coming from v2, you'll have to run bin/rails solid_cable:update to get a new migration for the channel index updates.

New Contributors

• @morgoth made their first contribution in #23

Full Changelog: v2.0.2...v3.0.0

v2.0.0

Breaking Changes

• Rename keep_messages_around_for to message_retention to pair with polling_interval by @dhh (#9)
• Enable autotrimming by @npezza93 (#11)
  • SolidCable::PruneJob -> SolidCable::TrimJob

v1.1.0

• Add a helper task for the installer by @dhh (#6)
• Simplify installer and keep async for development by @dhh (#7)

v1.0.0

• All configuration options have moved to config/cable.yml. config.solid_cable is no more
• Support installing using a different database
• Use insert instead of create when creating Messages. It's way faster and avoids transactions on mysql
• Add a migration to index chanels
• Remove pruning messages from disconnection. Add a separate job that can be run in the background to prune messages. Pruning on disconnection slowed things down a lot so easier to let the consumer enqueue the job themselves. Keeping messages around doesnt hurt anything.