Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled daily dependency update on thursday #518

Merged
merged 1 commit into from
Nov 2, 2017

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Nov 2, 2017

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

pynacl 1.1.2 » 1.2.0 PyPI | Changelog | Repo

Changelogs

pynacl 1.1.2 -> 1.2.0

1.2.0


  • Update libsodium to 1.0.15.
  • Infrastructure: add jenkins support for automatic build of
    manylinux1 binary wheels
  • Added support for SealedBox construction.
  • Added support for argon2i and argon2id password hashing constructs
    and restructured high-level password hashing implementation to expose
    the same interface for all hashers.
  • Added support for 128 bit siphashx24 variant of siphash24.
  • Added support for from_seed APIs for X25519 keypair generation.
  • Dropped support for Python 3.3.

That's it for now!

Happy merging! 🤖

@coveralls
Copy link

coveralls commented Nov 2, 2017

Coverage Status

Coverage remained the same at 99.293% when pulling 7f203a2 on pyup-scheduled-update-11-02-2017 into 844348e on develop.

Signed-off-by: Vladimir Diaz <vladimir.v.diaz@gmail.com>
@vladimir-v-diaz vladimir-v-diaz force-pushed the pyup-scheduled-update-11-02-2017 branch from 7f203a2 to 473c01a Compare November 2, 2017 19:45
@coveralls
Copy link

coveralls commented Nov 2, 2017

Coverage Status

Coverage remained the same at 99.293% when pulling 473c01a on pyup-scheduled-update-11-02-2017 into 844348e on develop.

@vladimir-v-diaz
Copy link
Contributor

@caniszczyk
I amended pyup-bot's commit to append a
Signed-off-by: Vladimir Diaz <vladimir.v.diaz@gmail.com>.

If I'm not mistaken, the DCO does allow a developer to sign-off on a contribution that they did not author.

This pull request should be good to merge now, however, the DCO probot requires that the signed-off-by entry match the commit author (see the failed check above). There is even an open pull request for this on the probot repo, where the commit.commiter is used instead of the commit.author during validation.

May I merge this pull request now that I've amended it? What do you recommend?

@caniszczyk
Copy link

merging this in now is fine, we need find a better story with bots

@vladimir-v-diaz
Copy link
Contributor

I'm happy to sign for soulless GitHub bots, but they're on their own once they become sentient.

@vladimir-v-diaz vladimir-v-diaz merged commit 69e996f into develop Nov 2, 2017
@vladimir-v-diaz vladimir-v-diaz deleted the pyup-scheduled-update-11-02-2017 branch April 13, 2018 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants