New version of rom (4.2.1) produced dependency conflicts #493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
✳️ 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:
Update CHANGELOGs [skip ci]
Update dependencies
Bump version to 4.2.1
Set upper bound for dry-types
[mapper] bump to 1.2.0
[core][mapper] update CHANGELOGs [ci skip]
[rom] update CHANGELOG [ci skip]
[core] update CHANGELOG [ci skip]
[rom] Update CHANGELOG [ci skip]