Turn off force_latest_compatible_version in README
#24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ChrisRackauckas, could you please take a quick look at this PR because you added the Resolver.jl based version of this action? |
But this suggests true in the README update? @StefanKarpinski is probably best to speak about how this argument in Pkg interacts with the resolver choice. |
Whoops, sorry, you are right. Fixed to suggest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In JuliaGeometry/MeshIntegrals.jl#205, I realized that
force_latest_compatible_versionneeds to be turned off because CompatHelper.jl PRs fail otherwise. See JuliaGeometry/MeshIntegrals.jl#205 (comment) for more details.