Skip to content

Commit

Permalink
Explain why the 1.4 package is installed despite the 1.2 compat entry
Browse files Browse the repository at this point in the history
  • Loading branch information
alecloudenback authored Mar 6, 2024
1 parent a14e436 commit fe7d054
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Bar = "0.1.2"
Often these compat entries get forgotten about once set. For instance, suppose the latest
version of Foo is v1.4.0, and your package now relies on some feature of Foo v1.4 that is
not present in Foo v1.2. Your package tests will still succeed, because by default they run
with the latest versions of all dependencies, including Foo v1.4.
with the latest versions of all dependencies, including Foo v1.4. This is because [Pkg.jl treats](https://pkgdocs.julialang.org/v1/compatibility/#Caret-specifiers) `"1.2.3"` is the same as `"^1.2.3"`, which allows the range of `[1.2.3, 2.0.0)`

This action will modify the compat to:
```toml
Expand Down

0 comments on commit fe7d054

Please sign in to comment.