This repository has been archived by the owner on Jan 7, 2024. It is now read-only.
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.
I'm preparing this release as we'll need to include it as a new dependency in
securedrop-client
for its next release.Testing
I've tested it by using
master
ofsecuredrop-client
with this branch of the SDK and the latest nightly ofsecuredrop-proxy
(https://apt-test.freedom.press/pool/main/s/securedrop-proxy/securedrop-proxy_0.2.1-dev-20200427-060417%2Bbuster_all.deb). I've verified I can successfully sync with a staging server with 1000 sources and done basic network operations (sent a reply successfully, downloaded a file/message/reply successfully).Next steps
Once this is merged, I'll do the next steps which are:
This also contains a change towards freedomofpress/securedrop-builder#144 (no longer uploading wheels to PyPI)