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 rails (5.2.0) produced dependency conflicts #1408

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 9, 2018

We've tested your project with an updated dependency and got errors while installing the dependencies.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name version specification new version
rails < 6.0, ~> 5.0 5.2.0

Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.

As this breaks fresh installs of your package, we've left this pull request open for you to investigate.

What changed?

✳️ rails ( → 5.2.0) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


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.

Depfu Status

@depfu depfu bot added the depfu label Apr 9, 2018
@tvdeyen
Copy link
Member

tvdeyen commented Apr 10, 2018

@depfu Already in the making #1387

@tvdeyen tvdeyen closed this Apr 10, 2018
@depfu depfu bot deleted the depfu/check/rails-5.2.0 branch April 10, 2018 20:22
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