Update puma: 4.3.5 → 4.3.6 (patch) #648
Merged
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ puma (4.3.5 → 4.3.6) · Repo · Changelog
Release Notes
4.3.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
v4.3.6
Merge pull request #2314 from venables/fix-include
Merge pull request #2269 from MSP-Greg/json-require
Release Notes
2.5.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Prepare for v2.5.4 release.
Remove unneeded assertions.
Update ext/nio4r/monitor.c
replace `if` with assert, keep memory init.
actually, initialize the whole memory block to zero
test allocation for failure and initialize memory
Add `if` statement, even if redundant
README.md: update build status badge
Move `EV_STANDALONE` definition to `extconf.rb` (#250)
Add space between control statements and brackets.
Use clang-format to improve code consistency.
Remove cruft from README.
Remove ancient Guardfile.
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