Releases: holochain/tryorama
Releases · holochain/tryorama
v0.15.4
v0.16.0-dev.3
Changed
- TryCP: Upgraded
tokio-tungstenite
to fix vulnerability.
Fixed
- Replace all IPv4 websocket addresses
127.0.0.1
bylocalhost
.
v0.16.0-dev.2
Changed
- Upgrade to latest JS client.
- Set allowed origins for admin websockets in Tryorama conductors and when attaching app websockets.
- Pass origin when connecting admin and app websockets.
v0.16.0-dev.1
Changed
- Upgrade JS client.
v0.15.3
v0.16.0-dev.0
Changed
- Upgrade deps to Holochain v0.3.0
v0.15.2
v0.15.1
Added
- Awaiting DHT sync: Add duplicated functions
conductorCellDhtSync
andisConductorCellDhtEqual
of existing functionsdhtSync
and make the prior versions aliases to these. New versions take in anIConductorCell
which just wraps anIConductor
andCellId
.
Fixed
- Security bump:
webpki
to v0.22.2 - Security bump:
@microsoft/api-extractor
to v7.36.2
v0.15.0
v0.15.0-rc.1
Changed
- BREAKING CHANGE: Upgrade to Holochain v0.3.0-beta-dev.8.
hc
output has changed which lead to local conductor startup refactoring. - BREAKING CHANGE:
runScenario
re-throws caught errors. - BREAKING CHANGE: To imitate a hApp client more closely in a test, App websockets are decoupled from conductors. This change plays out mainly on the conductor level, but a player contains the app agent websocket now too for registering signals. Previously there used to be a single app websocket per conductor for all of its agents. Now there is one app agent websocket connection per agent.
- TryCP scenario: Optimize multi client/multi player installation. All agent app installations for a conductor and all conductor installations for a client are triggered in parallel instead of sequentially.
Fixed
- BREAKING CHANGE: Awaiting DHT sync of multiple players received a more universal API. Scenario methods were removed, so that in all cases the util function must be called.