#19 changed how pubsub subscriptions are listed from:

const subscriptions = await this._pubsub.ls()

to

const subscriptions = await this._pubsub.getTopics()

This in effect forces the user to upgrade to a newer version of whatever libp2p-pubsub subclass they are using but also arrives as a stealth upgrade if your package.json contains ^0.2.1 as the version for this module.

This is not a backwards compatible change so should not be a patch release.

Please revert #19, republish v0.2.1 as v0.2.3, then reapply #19 and publish it as 0.3.0.

If I call get for the same key, it'll call pubsub.subscribe and add another handler for the same key.

I think we only want one handler per key right?

The main purpose of this module is to be used with TieredDatastore. Accordingly, all the methods that may used by this Datastore should be implemented, in order to guarantee that no unexpected problems may occur.

With all this methods implemented, this datastore should also run interface-datastore tests against this, like here.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Currently this module is called datastore-pubsub and in theory it should follow the ipfs/interface-datastore and also be compatible with the DHT API, to be used on a TieredDatastore.

This issue aims to track the discussion if we should rename the module and what it should be compatible with.

Context: #60

Is there an equivalent golang package?

I found https://github.com/libp2p/go-libp2p-pubsub-router but was hoping to get some clarification what the relationship is? Or perhaps I'm missing something obvious.