Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up[ruby] Update daemons: 1.3.0 → 1.3.1 (patch) #233
+1
−1
Conversation
depfu
bot
added
the
depfu
label
Dec 15, 2018
This comment has been minimized.
This comment has been minimized.
codecov-io
commented
Dec 16, 2018
•
Codecov Report
@@ Coverage Diff @@
## master #233 +/- ##
=======================================
Coverage 92.49% 92.49%
=======================================
Files 35 35
Lines 533 533
=======================================
Hits 493 493
Misses 40 40 Continue to review full report at Codecov.
|
ruebot
merged commit cd0a9c0
into
master
Dec 20, 2018
depfu
bot
deleted the
depfu/update/daemons-1.3.1
branch
Dec 20, 2018
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.
depfu bot commentedDec 15, 2018
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?
Release Notes
1.3.1
Bugfix release:
Commits
See the full diff on Github. The new version differs by 4 commits:
Bump version to 1.3.1
Merge pull request #73 from iNecas/fix-pidfile
Remove date from gemspec
Fix undefined local variable or method `pid_delimiter'
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