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 rom (4.2.1) produced dependency conflicts #493

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Jul 27, 2018

We've tried to upgrade a dependency and got errors running Bundler.

name version specification new version
rom >= 3.3.3, ~> 3.3 4.2.1

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 "rom":
  In Gemfile:
    rom (>= 3.3.3, ~> 4.2)

    rom-sql (>= 1.3.5, ~> 1.3) was resolved to 1.3.5, which depends on
      rom (>= 3.2.2, ~> 3.2)

What changed?

✳️ rom ( → 4.2.1) · Repo · Changelog

Release Notes

From the Github release:

v4.2.1 2018-05-03

  • rom-core updated to ['~> 4.2', '>= 4.2.1']

Compare v4.2.0...v4.2.1

rom-core v4.2.1

v4.2.1 2018-05-03

  • dry-types dependency is constrained with ~> 0.12.1

rom-mapper 1.2.1 2018-05-03

  • dry-types dependency is constrained with ~> 0.12.1
Commits

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

@depfu depfu bot added the depfu label Jul 27, 2018
@jodosha jodosha self-assigned this Jul 27, 2018
@jodosha
Copy link
Member

jodosha commented Jul 27, 2018

Closing in favor of #490

@jodosha jodosha closed this Jul 27, 2018
@depfu depfu bot deleted the depfu/update/rom-4.2.1 branch July 27, 2018 10:17
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.

1 participant