Apply Version Updates From Current Changes #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version Updates
Merging this PR will release new versions of the following packages based on your change files.
stronghold-derive
[0.3.0]
Implement API for the Stronghold Procedures, see PR 258 for details.
stronghold-runtime
[0.4.0]
stronghold-engine
[0.5.0]
Update inline Docs and README files to reflect the current state of the project.
Add communication fuzzer for distributed fuzzing with docker.
Patch Stronghold engine fuzzer.
Patch crypto.rs version v0.7 -> v0.8.
[PR 269]
Refactor Error types in engine and client:
Add differentiated error types for the different methods
Avoid unwraps in the engine
Remove the single, crate-wide used error types of engine and client
Remove
anyhow
Error types in client and bubble up the actual error insteadAdd nested Result type alias
StrongholdResult<T> = Result<T, ActorError>
for interface errorsd6b814dd Add Changelog for PR 269 on 2021-11-03
stronghold-utils
[0.4.0]
Extract
random
functions fromtest_utils
into own module.stronghold-p2p
[0.3.1]
[PR 276]
Remove
relay
andmdns
features.In the
StrongholdP2p
Interface enable / disable mdns and relay functionality on init via config flags in theStrongholdP2pBuilder
.Per default, both are enabled.
In the
Stronghold
client interface enable / disable mdns and relay in theNetworkConfig
when spawning a new p2p-network actor.Per default, both are disabled.
8cbb8944 Add changelog on 2021-10-29
679cf029 feat(client): mdns/relay config in Stronghold client on 2021-11-01
libp2p::swarm::toggle
to enable/ disable relay and mdns[PR 271]
Patch libp2p version from v0.39 to v0.40.0-rc.2.
[PR 290]
Persist the state of stronghold-p2p in the
SecureClient
by serializing theNetworkConfig
and writing it to the store.Allow loading stored states into the
NetworkActor
on init.Allow reuse of same
Keypair
that is stored in the vault.83903c7e Add changelog for p2p/persist-config on 2021-11-16
iota-stronghold
[0.5.0]
introduced registry actor for clients as service
introduced snapshot actor as service
merge
Internal
andClient
-Actors intoSecureClient
api change in interface for test reading secrets out of a vault. minimal impact.
e8b10eac feat: Migrating stronghold from riker actor system implementation to actix. client + internal actor have been merged. Message types are transformed into structs. on 2021-08-23
[PR 270]
Move management of network-Actor and client-target into Registry
Make client-target optional, in case that it is killed before switching to another target
Make registry a normal actor instead of a system-service
a4cb0152 doc(client): Add changelog on 2021-10-26
CopyRecord
procedure.Update inline Docs and README files to reflect the current state of the project.
actors::secure::StoreError::NotExisting
as proper error type for correct error handling in client.[PR 254]
Change key handling in the
SecureClient
to avoid unnecessary cloning of keys.Remove obsolete VaultId-HashSet from the
SecureClient
.[PR 276]
Remove
relay
andmdns
features.In the
StrongholdP2p
Interface enable / disable mdns and relay functionality on init via config flags in theStrongholdP2pBuilder
.Per default, both are enabled.
In the
Stronghold
client interface enable / disable mdns and relay in theNetworkConfig
when spawning a new p2p-network actor.Per default, both are disabled.
8cbb8944 Add changelog on 2021-10-29
679cf029 feat(client): mdns/relay config in Stronghold client on 2021-11-01
Patch crypto.rs version v0.7 -> v0.8.
[PR 290]
Persist the state of stronghold-p2p in the
SecureClient
by serializing theNetworkConfig
and writing it to the store.Allow loading stored states into the
NetworkActor
on init.Allow reuse of same
Keypair
that is stored in the vault.83903c7e Add changelog for p2p/persist-config on 2021-11-16
[PR 285]
Implement messages to write the keypair used for
StrongholdP2p
in the vault and derive thePeerId
and a new noiseAuthenticKeypair
from it.[PR 258]
Implement API for the Stronghold Procedures, see PR 258 for details.
[PR 269]
Refactor Error types in engine and client:
Add differentiated error types for the different methods
Avoid unwraps in the engine
Remove the single, crate-wide used error types of engine and client
Remove
anyhow
Error types in client and bubble up the actual error insteadAdd nested Result type alias
StrongholdResult<T> = Result<T, ActorError>
for interface errorsd6b814dd Add Changelog for PR 269 on 2021-11-03
write_to_vault
always returned an error even if the operation was successful.commandline
[0.1.3]
introduced registry actor for clients as service
introduced snapshot actor as service
merge
Internal
andClient
-Actors intoSecureClient
api change in interface for test reading secrets out of a vault. minimal impact.
Bumped due to a bump in iota-stronghold.
e8b10eac feat: Migrating stronghold from riker actor system implementation to actix. client + internal actor have been merged. Message types are transformed into structs. on 2021-08-23
[PR 270]
Move management of network-Actor and client-target into Registry
Make client-target optional, in case that it is killed before switching to another target
Make registry a normal actor instead of a system-service
Bumped due to a bump in iota-stronghold.
a4cb0152 doc(client): Add changelog on 2021-10-26
CopyRecord
procedure.Update inline Docs and README files to reflect the current state of the project.
actors::secure::StoreError::NotExisting
as proper error type for correct error handling in client.[PR 254]
Change key handling in the
SecureClient
to avoid unnecessary cloning of keys.Remove obsolete VaultId-HashSet from the
SecureClient
.[PR 276]
Remove
relay
andmdns
features.In the
StrongholdP2p
Interface enable / disable mdns and relay functionality on init via config flags in theStrongholdP2pBuilder
.Per default, both are enabled.
In the
Stronghold
client interface enable / disable mdns and relay in theNetworkConfig
when spawning a new p2p-network actor.Per default, both are disabled.
Bumped due to a bump in iota-stronghold.
8cbb8944 Add changelog on 2021-10-29
679cf029 feat(client): mdns/relay config in Stronghold client on 2021-11-01
Patch crypto.rs version v0.7 -> v0.8.
[PR 290]
Persist the state of stronghold-p2p in the
SecureClient
by serializing theNetworkConfig
and writing it to the store.Allow loading stored states into the
NetworkActor
on init.Allow reuse of same
Keypair
that is stored in the vault.Bumped due to a bump in iota-stronghold.
83903c7e Add changelog for p2p/persist-config on 2021-11-16
[PR 285]
Implement messages to write the keypair used for
StrongholdP2p
in the vault and derive thePeerId
and a new noiseAuthenticKeypair
from it.[PR 258]
Implement API for the Stronghold Procedures, see PR 258 for details.
[PR 269]
Refactor Error types in engine and client:
Add differentiated error types for the different methods
Avoid unwraps in the engine
Remove the single, crate-wide used error types of engine and client
Remove
anyhow
Error types in client and bubble up the actual error insteadAdd nested Result type alias
StrongholdResult<T> = Result<T, ActorError>
for interface errorsBumped due to a bump in iota-stronghold.
d6b814dd Add Changelog for PR 269 on 2021-11-03
write_to_vault
always returned an error even if the operation was successful.