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 docopt (0.6.0) broke the build #16

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Oct 13, 2017

Hello,

We've tested your project with an updated dependency and the build failed.

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.

gem name version specification new version
docopt ~> 0.5 0.6.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure potentially will also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of docopt for this test run.

What changed?

✳️ docopt ( → 0.6.0) · Repo

Sorry, we couldn't find anything useful about this release.


Depfu sends automated pull requests to update your Ruby dependencies.

@depfu depfu bot added the depfu label Oct 13, 2017
@DannyBen
Copy link
Owner

Docopt 0.6 changes a behavior in an undesired way. Avoiding this upgrade until they fix it.

@DannyBen DannyBen closed this Oct 13, 2017
@depfu depfu bot deleted the depfu/check/docopt-0.6.0 branch October 13, 2017 12:35
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