Don't make PRs to packages that have a dependency that upper bounds the package CompatHelper bumps

[KristofferC]

The tests will then still use the old version and not be effective in knowing if the package actually is compatible with the old version.

[DilumAluthge]

I agree. I’m just not sure how to implement this.

[colinxs]

What about:

1. Create a temp copy of the project.
2. Delete all [compat] entries except for julia
3. Pkg.update()
4. Read back the versions in the updated manifest.

That should get you the latest possible versions of all packages while respecting the upper bounds of dependencies, right?

[tkf]

It's like what @colinxs already said but, instead of adding this feature in CompatHelper.jl, can we have a mode in Pkg.add (and Pkg.test) to ignore indirect compat bounds if they prevent updating direct dependencies?

[KristofferC]

I'm happy with exploring different non-default modes for the resolver. The logic would be around here:

https://github.com/JuliaLang/Pkg.jl/blob/a9d85e7b8a22b1f0fe8cdbdfa4fe9d5f60ee5ea0/src/Operations.jl#L425-L431

[timholy]

Here's a screenshot of my inbox:

😆

[DilumAluthge]

It is worth figuring out how to reduce these notifications.

Certainly one solution would be to have a single pull request for all suggested changes, instead of a different pull request for each suggested change: #126

[timholy]

That would be a great change. But waiting to submit the PR until the resolver will actually use the version whose bounds are loosening is also useful. The main reason these are hanging around in my inbox is that these are the ones I couldn't deal with immediately because I needed to work my way up the hierarchy of dependencies.