Skip to content

Releases: ssbc/ssb-db

v20.3.0

04 Aug 00:30
Compare
Choose a tag to compare

new features:

  • db.addBoxer API changed so that boxer is now provided with the previous messageId of last know message (required for ssb-tribes)
  • db.getFeedState(feedId, cb) provided for accessing previous message state (including previous messages queued for persistence)

bugs fixes:

  • bulk publishing of > 1000 messages now working reliably
  • private group auto-boxing fixed (by new features above)
  • fixed test suite running on windows

v20.2.0

04 Aug 00:36
Compare
Choose a tag to compare

features added:

  • added an LRU cache over unboxer
  • added mac + win test to travis
  • modify addBoxer to take an init method, modify db methods to wait for boxer initialisation (where required)

fixes / maintenance:

  • fixed test suite so all tests are running + passing
  • refactored some tests + clearly named all tests
  • updated some deps : mkdirp, flumedb, ssb-ref, tape

v20.1.0

11 Jun 03:23
Compare
Choose a tag to compare

this release:

  • exposes the rebuild function, which allows you to trigger a rebuild of all the flume indexes attached to ssb-db

v20.0.1

11 Jun 02:46
Compare
Choose a tag to compare

This release:

  • exposes addBoxer / addUnboxer methods with initialisation step
  • extracts ssb-private1 as a standalone module for boxing / unboxing.
    • developers can now choose whether to include this in their stack
    • ⚠️ you will need to rebuild your indexes each time you include a new unboxer
  • adds additional tests around boxing/ unboxing

Breaking changes

If you want to update ssb-db and keep using it with all the same features you had before (e.g. including classic private messages), you also need to include ssb-private1, like this:

  .use(require('ssb-db'))
  .use(require('ssb-private1'))

v20.0.0

11 Jun 02:41
Compare
Choose a tag to compare

deprecated

this release exposed unboxed message on some methods which other plugins were exposing