You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the
service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* Our friends at [Travis-CI](https://travis-ci.com) provide excellent service.
* [Circle CI](https://circleci.com) are good, too, and have a free plan that will cover basic needs.
* If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
* If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.
It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.
We've updated a dependency and here is what you need to know:
name
version specification
old version
new version
github-pages
185
186
Additionally, the update changed a few other dependencies as well:
action
name
old version
new version
updated
activesupport
4.2.9
4.2.10
updated
faraday
0.15.1
0.15.2
updated
unicode-display_width
1.3.2
1.3.3
You should probably take a good look at the info here and the test results before merging this pull request, of course.
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.
⚠️ No CI detected ⚠️
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* Our friends at [Travis-CI](https://travis-ci.com) provide excellent service. * [Circle CI](https://circleci.com) are good, too, and have a free plan that will cover basic needs. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.
We've updated a dependency and here is what you need to know:
Additionally, the update changed a few other dependencies as well:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ github-pages (185 → 186) · Repo
Release Notes
From the Github release:
ActiveSupport v4.2.10 (#559)
Nokogiri 1.8.2 or greater (#563)
↗️ activesupport (indirect, 4.2.9 → 4.2.10) · Repo · Changelog
↗️ faraday (indirect, 0.15.1 → 0.15.2) · Repo · Changelog
Release Notes
From the Github release:
Net::HTTPadapters to retry request internally by settingmax_retriesto 0 if available (Ruby 2.5+). (#799)NestedParamsEncoderhandling of empty array values (#801)Commits
See the full diff on Github. The new version differs by 3 commits:
Version bump to 0.15.2#800 correct handling parameter value empty array (#801)Set max_retries to 0 if available. (#799)↗️ unicode-display_width (indirect, 1.3.2 → 1.3.3) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 3 commits:
Release v1.3.3Clarify supported RubiesReplace Gem::Util.gunzip with direct zlib implementationDepfu 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.