This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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.
Add Decimal.Context.with/2, Decimal.Context.get/1, Decimal.Context.set/2,
and Decimal.Context.update/1
Add Decimal.is_decimal/1
Deprecations
Deprecate Decimal.minus/1 in favour of the new Decimal.negate/1
Deprecate Decimal.plus/1 in favour of the new Decimal.apply_context/1
Deprecate Decimal.reduce/1 in favour of the new Decimal.normalize/1
Deprecate Decimal.with_context/2, Decimal.get_context/1, Decimal.set_context/2,
and Decimal.update_context/1 in favour of new functions on the Decimal.Context module
Deprecate Decimal.decimal?/1 in favour of the new Decimal.is_decimal/1
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:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options.
* 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/`.
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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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?
✳️ excoveralls (0.13.0 → 0.13.1) · Repo · Changelog
Release Notes
0.13.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Bump version and update CHANGELOGMerge pull request #226 from diogommartins/fix/mocked-module-handlingFixing mocked modules coverage handling↗️ decimal (indirect, 1.8.1 → 1.9.0) · Repo · Changelog
Release Notes
1.9.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
Release v1.9.0Update ex_docPrepare v1.9.0-rc.0 (#140)Use SPDX license identifierDeprecate cast/1 (#138)Explain idiomatic API in docsMove modules to individual filesFix is_decimal/1 in guardsAdd Decimal.is_decimal/1 and deprecate Decimal.decimal?/1 (#133)Deprecate Decimal.*context functions in favour of new ones on Decimal.Context (#137)Add Decimal.normalize/1 and deprecate Decimal.reduce/1 (#136)Add Decimal.apply_context/1 and deprecate Decimal.plus/1 (#135)Add Decimal.negate/1 and deprecate Decimal.minus/1 (#134)Deprecate Decimal.compare/2 in favour of Decimal.cmp/2 (#132)Update changelogStart v1.9.0-dev↗️ jason (indirect, 1.2.1 → 1.2.2) · Repo · Changelog
Release Notes
1.2.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Release 1.2.2Support Decimal 2.x (#114)Migrate CI from Travis to GitHub Actions, adding recommended Elixir and Erlang/OTP combinations (#112)👉 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:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * 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/`.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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.