We've tried to upgrade a dependency and got errors running Bundler. It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.
Please take a look at the exact failure to figure out if this is something you need to work on.
The bundler error message was:
Bundler could not find compatible versions for gem "capybara":
In Gemfile:
hanami-devtools was resolved to 0.1.0, which depends on
capybara (= 3.15.1)
hanami-devtools was resolved to 0.1.0, which depends on
poltergeist (~> 1.17) was resolved to 1.18.1, which depends on
capybara (< 4, >= 2.1)
Bundler could not find compatible versions for gem "dry-logic":
In Gemfile:
dry-logic (< 0.5, ~> 0.4.2)
dry-validation (<= 1.3.0, ~> 1.3) was resolved to 1.3.0, which depends on
dry-schema (>= 1.3.1, ~> 1.0) was resolved to 1.3.3, which depends on
dry-logic (~> 1.0)
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 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)
depfu[bot]
commented
5 years ago
We've tried to upgrade a dependency and got errors running Bundler. It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.
Please take a look at the exact failure to figure out if this is something you need to work on.
The bundler error message was:
What changed?
✳️ dry-validation (~> 0.11, < 0.12 → ~> 1.3, <= 1.3.0) · Repo · Changelog
Release Notes
1.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Bump dry-validation to 1.3.0Update CHANGELOG [ci skip]Fix guarding rules with nested values specified as a hash (#579)Merge pull request #580 from dry-rb/574-support-for-setting-external-schemasAdd support for setting an external schemaMerge pull request #577 from esparta/use_fetch_values_on_valuesAdding test for non-existing key on Dry::Validations::Value#[]Update lib/dry/validation/values.rbdry/validations/values/#[] - Use fetch_values on final mapMerge pull request #575 from dry-rb/enhancement/dsl-schema-getterLet `Dry::Validation::Contract.schema`, `.params`, and `.json` to return defined schema when invoked without blockDepfu 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