Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version of dry-validation (1.4.2) produced dependency conflicts #193

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 19, 2020

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 (>= 2.1, < 4)

Bundler could not find compatible versions for gem "dry-logic":
  In Gemfile:
    dry-logic (~> 0.4.2, < 0.5)

    dry-validation (~> 1.4, <= 1.4.2) was resolved to 1.4.0, which depends on
      dry-schema (~> 1.0, >= 1.3.1) was resolved to 1.4.3, which depends on
        dry-logic (~> 1.0)

What changed?

✳️ dry-validation (~> 0.11, < 0.12 → ~> 1.4, <= 1.4.2) · Repo · Changelog

Release Notes

1.4.2 (from changelog)

Fixed

  • Macros using predicates that accept a range argument work as expected (no need to wrap the argument in an array) (@waiting-for-dev)

Compare v1.4.1...v1.4.2

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 56 commits:


Depfu Status

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)

@depfu depfu bot added the depfu label Jan 19, 2020
@depfu
Copy link
Contributor Author

depfu bot commented Mar 12, 2020

Closed in favor of #195.

1 similar comment
@depfu
Copy link
Contributor Author

depfu bot commented Mar 12, 2020

Closed in favor of #195.

@depfu depfu bot closed this Mar 12, 2020
@depfu depfu bot deleted the depfu/update/dry-validation-1.4.2 branch March 12, 2020 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants