-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: SubstituteAlert/bcrypt-ruby
base: master
head repository: bcrypt-ruby/bcrypt-ruby
compare: master
- 12 commits
- 6 files changed
- 1 contributor
Commits on Dec 31, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 27dbab3 - Browse repository at this point
Copy the full SHA 27dbab3View commit details -
Configuration menu - View commit details
-
Copy full SHA for c156254 - Browse repository at this point
Copy the full SHA c156254View commit details -
Merge pull request bcrypt-ruby#287 from tenderlove/modernize-ci
try to modernize CI
Configuration menu - View commit details
-
Copy full SHA for eba09de - Browse repository at this point
Copy the full SHA eba09deView commit details -
We have a test that tries to test the "calibration" function in BCrypt. This function is supposed to return a "cost" based on some number of milliseconds passed in. We're trying to make the cost relative to some beginning cost (MIN_COST + 1), time that, then use it as the "relative time". The problem is that the time this takes in CI is not constant, so even `min_time_ms * 4` may fit inside the same "cost" as the original. I'm bumping the factor to `5` to hopefully reduce the flakiness. It seems like we just want to test that "some time deadline" returns a greater cost than a different time deadline, so I think bumping the factor to 5 is a legit fix
Configuration menu - View commit details
-
Copy full SHA for d94041a - Browse repository at this point
Copy the full SHA d94041aView commit details -
Merge pull request bcrypt-ruby#288 from tenderlove/deal-with-flake
Try to deal with flaky tests
Configuration menu - View commit details
-
Copy full SHA for ca9cea1 - Browse repository at this point
Copy the full SHA ca9cea1View commit details -
This way we can just push a tag and let GitHub actions do the release
Configuration menu - View commit details
-
Copy full SHA for 344ca59 - Browse repository at this point
Copy the full SHA 344ca59View commit details -
Merge pull request bcrypt-ruby#289 from tenderlove/trusted-publishers
Configure trusted publishing
Configuration menu - View commit details
-
Copy full SHA for da89a83 - Browse repository at this point
Copy the full SHA da89a83View commit details -
Configuration menu - View commit details
-
Copy full SHA for 64605fc - Browse repository at this point
Copy the full SHA 64605fcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b1fc73 - Browse repository at this point
Copy the full SHA 4b1fc73View commit details -
Merge pull request bcrypt-ruby#290 from tenderlove/bump
bump version
Configuration menu - View commit details
-
Copy full SHA for 82e6c4c - Browse repository at this point
Copy the full SHA 82e6c4cView commit details -
Move compilation after bundle install
The Rakefile depends on gems being installed. Hopefully this will fix JRuby releases on trusted publishing
Configuration menu - View commit details
-
Copy full SHA for 01cc688 - Browse repository at this point
Copy the full SHA 01cc688View commit details -
Merge pull request bcrypt-ruby#291 from tenderlove/fix-publishing
Move compilation after bundle install
Configuration menu - View commit details
-
Copy full SHA for 36a04a2 - Browse repository at this point
Copy the full SHA 36a04a2View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master