fix(plugin-ledger-connector-fabric-socketio): upgrade Fabric due to jsrsasign

[outSH]

Revert fabric sdk package change from PR #1754

Closes: #1799
Signed-off-by: Michal Bajer michal.bajer@fujitsu.com

After change:

@hyperledger/cactus@ /home/outsh/cactus
├─┬ @hyperledger/cactus-cmd-socket-server@1.0.0-rc.3 -> ./packages/cactus-cmd-socketio-server
│ └─┬ fabric-ca-client@1.4.19
│   └── jsrsasign@10.5.0
├─┬ @hyperledger/cactus-example-carbon-accounting-backend@1.0.0-rc.3 -> ./examples/cactus-example-carbon-accounting-backend
│ └─┬ fabric-network@2.2.10
│   └─┬ fabric-common@2.2.10
│     └── jsrsasign@10.5.0 deduped
├─┬ @hyperledger/cactus-plugin-ledger-connector-fabric-socketio@1.0.0-rc.3 -> ./packages/cactus-plugin-ledger-connector-fabric-socketio
│ └─┬ fabric-client@1.4.19
│   └── jsrsasign@10.5.0 deduped
├─┬ @hyperledger/cactus-plugin-ledger-connector-fabric@1.0.0-rc.3 -> ./packages/cactus-plugin-ledger-connector-fabric
│ ├─┬ fabric-ca-client@2.3.0-snapshot.62
│ │ └── jsrsasign@10.5.0
│ ├─┬ fabric-common@2.3.0-snapshot.63
│ │ └── jsrsasign@10.5.0 deduped
│ ├── jsrsasign@10.4.0
│ └─┬ ws-wallet@1.1.5
│   └── jsrsasign@10.4.1
└─┬ @hyperledger/cactus-test-tooling@1.0.0-rc.3 -> ./packages/cactus-test-tooling
  └─┬ fabric-ca-client@2.2.10
    ├─┬ fabric-common@2.2.10
    │ └── jsrsasign@10.5.0 deduped
    └── jsrsasign@10.5.0 deduped

[izuru0]

LGTM

[outSH]

@petermetz Can you approve and merge this please? It's blocking PR next in line :)

[petermetz]

@petermetz Can you approve and merge this please? It's blocking PR next in line :)

@outSH Thank you for the information. I'm working on the reviews as fast as I can. :)

[petermetz]

@petermetz Oh, right! I'm currently working on putting them into containers and monorepo build right now, and for some reasons assumed it's already done in my mind :)

Thank you! I vote for exact versions, regardless of it being more effort to manually bump them later or not.

@outSH No worries, I mix up my own PRs all the time. Extending on my earlier answer: the yarn.lock wouldn't save us in some edge cases either and because of that I always ask people to specify exact versions instead of ranges (so I would've asked the same thing even if the packages were part of the monorepo already)

OK. Shall I switch to exact versions for every dependency in package.json? Only fabric one? Shall I do this for all package.json affected by this PR?

That can be part of another PR, I dont' want to complicate this one any further.

[outSH]

Thank you for the information. I'm working on the reviews as fast as I can. :)

Sure, not rushing, I just wanted to put this PR to the front ;) Thank's for quick handling other PR as well, btw