Update v15 - Githubissues

ssbc / ssb-server

The gossip and replication server for Secure Scuttlebutt - a distributed social network

1.68k stars 164 forks source link

Update v15 #739

Closed clehner closed 3 years ago

clehner commented 3 years ago

Since #734, I am using and recommending ssb-server v15 over v16.

I would like to publish a new patch release of v15 with the following changes:

Update ssb-links to v3.0.10, as in #738
Update chloride to v2.3.0, to bring in in sodium-native v3, supporting Node v12+
Backport #727 and #432, for good measure

There are no indexing conflicts that I am aware of between v15 and v16 currently - v16 just adds ssb-private1 - so it is safe to run both of these with the same ~/.ssb directory (not at the same time, of course). Running v15 is useful for recovering from #734.

ahdinosaur commented 3 years ago

merging, as i'm keen to upgrade ssb-pub with this release.

ref: https://github.com/ahdinosaur/ssb-pub/issues/37

ahdinosaur commented 3 years ago

hm, i made a new version 15.3.0, but not sure how to npm publish, npm test and specifically compatibility seems to always end on an error. i see https://github.com/ssbc/ssb-server/pull/628#issuecomment-459640976, but not sure how to resolve.

ahdinosaur commented 3 years ago

yeah, seems like we're in a situation with:

when two plugins have a dev dep that conflicts, the pretest script fails. a@2 a@3 would fail, it this case you will need to fix the plugins.

oh no, shaving yaks...

ssb-ebt wants:
- cat-names@3
- dog-names@2
ssb-replicate wants:
- cat-names@2
- dog-names@1

vs.

ssb-ooo wants:
- rimraf@3
ssb-blobs wants:
- rimraf@2

ahdinosaur commented 3 years ago

well compatibility cycles between two sets of dev dependencies. both of them pass, so do i yolo and force publish? :smiley_cat: i'll make some lunch.

ahdinosaur commented 3 years ago

published ssb-server@15.3.0 :tada:

clehner commented 3 years ago

Thanks @ahdinosaur