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

Update rbnacl requirement from ~> 3.4.0 to >= 3.4, < 7.1 #2

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Aug 23, 2019

Updates the requirements on rbnacl to permit the latest version.

Changelog

Sourced from rbnacl's changelog.

3.4.0 (2015-05-07)

  • Expose RbNaCl::Signatures::Ed25519#keypair_bytes (#135)
  • Expose HMAC-SHA512 with 64-byte keys (#137)

3.3.0 (2015-12-29)

  • Remove use of Thread.exclusive when initializing library (#128)
  • Add salt/personalisation strings for Blake2b (#105)

3.2.0 (2015-05-31)

  • Fix method signature for blake2b
  • RuboCop-friendly codebase

3.1.2 (2014-08-30)

  • Fix scrypt support with libsodium 0.7.0 (scryptsalsa208sha256)

3.1.1 (2014-06-14)

  • Fix undefined variable warning
  • RSpec 3 fixups
  • RuboCop

3.1.0 (2014-05-22)

  • The scrypt password hashing function: RbNaCl::PasswordHash.scrypt

3.0.1 (2014-05-12)

  • Load gem from RBNACL_LIBSODIUM_GEM_LIB_PATH if set. Used by rbnacl-libsodium
    gem to use libsodium compiled from a gem.

3.0.0 (2014-04-22)

  • Rename RandomNonceBox to SimpleBox (backwards compatibility preserved)
  • Reverse documented order of SimpleBox/RandomNonceBox initialize parameters.
    Technically backwards compatible, but confusing.
  • Ensure all strings are ASCII-8BIT/BINARY encoding prior to use

2.0.0 (2013-11-07)

  • Rename Crypto module to RbNaCl module
  • Add encrypt/decrypt aliases for Crypto::RandomNonceBox
  • RbNaCl::VerifyKey#verify operand order was reversed. New operand order is
    signature, message instead of message, signature
  • RbNaCL::SecretBox#open, RbNaCl::Box#open, Auth#verify and
    VerifyKey#verify all now raise a (descendent of) CryptoError if the check
    fails. This ensures failures are handled by the program.
... (truncated)
Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Aug 23, 2019
@coveralls
Copy link

coveralls commented Aug 23, 2019

Coverage Status

Coverage decreased (-96.2%) to 3.846% when pulling 681eb5f on dependabot/bundler/rbnacl-gte-3.4-and-lt-7.1 into 6d012e2 on master.

Updates the requirements on [rbnacl](https://github.com/crypto-rb/rbnacl) to permit the latest version.
- [Release notes](https://github.com/crypto-rb/rbnacl/releases)
- [Changelog](https://github.com/crypto-rb/rbnacl/blob/master/CHANGES.md)
- [Commits](RubyCrypto/rbnacl@v3.4.0...v3.4.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot force-pushed the dependabot/bundler/rbnacl-gte-3.4-and-lt-7.1 branch from 6b6cf18 to 681eb5f Compare August 23, 2019 17:54
@dependabot-preview
Copy link
Contributor Author

Looks like rbnacl is up-to-date now, so this is no longer needed.

@dependabot-preview dependabot-preview bot deleted the dependabot/bundler/rbnacl-gte-3.4-and-lt-7.1 branch August 23, 2019 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant