Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up[ruby] Update rack: 2.1.1 → 2.1.2 (patch) #363
Merged
+1
−1
Conversation
This comment has been minimized.
This comment has been minimized.
codecov
bot
commented
Jan 29, 2020
•
Codecov Report
@@ Coverage Diff @@
## master #363 +/- ##
=======================================
Coverage 89.15% 89.15%
=======================================
Files 35 35
Lines 636 636
=======================================
Hits 567 567
Misses 69 69 Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
depfu bot commentedJan 29, 2020
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?
Commits
See the full diff on Github. The new version differs by 8 commits:
Bump for 2.1.2 release
Update changelog in preparation for 2.1.2
Fix multipart parser for special files #1308
Fix `use` with kwargs
Skip deflating in Rack::Deflater if Content-Length is 0
#transform_keys no longer necessary, reverts #1401
Fix: Add to_hash to wrap Hash and Session classes
Handle case where session id key is requested but it is missing
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