Closed staltz closed 2 years ago
@arj03 If you don't mind, there are a bunch of modules that need this same kind of boring PR to bump ssb-db2, can I just push the bump commit to master and publish new versions on those modules? Or do you prefer to see the PRs for each?
Context
There are a bunch of modules (such as
ssb-friends
), which requiressb-db2
. If I update myssb-db2
dependency to3.0.0
, then all these other modules would still pull inssb-db2
at2.x
, because of the^
in^2.1.0
.Problem and solution
Update ssb-db2 to 3.0.0 even though the breaking change does not affect ssb-friends in any way.
Side comment
I also pinned
envelope-spec
to 1.0.0 because apparently there was a breaking change from 1.0.0 to 1.1.0, where thetfk.json
file was removed. Sincessb-tribes@0.4.1
was importingenvelope-spec
as^1.0.0
, I was getting an errorError: Cannot find module 'envelope-spec/encoding/tfk.json'
.