New version of bcrypt (3.1.17) produced dependency conflicts #3
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.
We've tested your project with an updated dependency and got errors while installing the dependencies.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.
As this breaks fresh installs of your package, we've left this pull request open for you to investigate.
What changed?
✳️ bcrypt (~> 3.1.7 → 3.1.17) · Repo · Changelog
Release Notes
3.1.17 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 40 commits:
Update for release
Merge pull request #243 from JoshCheek/prefix-value
Merge pull request #257 from petergoldstein/feature/add_ruby_3_1_to_ci
Add Ruby 3.1 to CI
Merge pull request #255 from asavageiv/alan/long-passwords
test: Simplify password create tests for long secrets
test: Reword hash_secret specs for clarity
Truncate based on bytesize instead of number of chars
Switch from 255 char max to 72
Truncate secrets greater than 255 chars in hash_secret
Add a test demonstrating passwords >255 chars fail
Merge pull request #253 from athix/feature/build-status-badge
Update README build status badge
Remove .travis.yml (unused)
Minor whitespace fixes
Merge pull request #252 from athix/feature/github-actions
Include doesn't work as expected
Remove mswin and try using include instead of exclude for mingw
Fine tune exclusions
Add windows to github action and remove jruby from ubuntu matrix
Use latest setup-ruby and add mingw/mswin
Use default rake task
Add Github Action
Some URL updates now that this has moved to an org
Merge pull request #247 from athix/feature/document-edge-case
Document all possible permutations
Document BCrypt::Password#== edge case/gotcha
Make the prefix less sus
Merge pull request #121 from kachick/fix-regex-in-validator
Merge pull request #242 from kachick/ignore-gemfilelock
Fix a regex in Bcrypt::Password.valid_hash? and Bcrypt::Engine.valid_salt?
Ignore Gemfile.lock in git
Merge pull request #241 from shmokmt/improve-readme
Update version
Merge pull request #240 from timcraft/patch-1
Test on ruby 3.0
Make min time difference still x4
Merge pull request #223 from bjfish/add-truffleruby-to-ci
Merge pull request #236 from mmccarthy15/master
additional changelog comment
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands