From fe7d054cf8fab41849195c08ffbeb817b9cbf80c Mon Sep 17 00:00:00 2001 From: alecloudenback Date: Tue, 5 Mar 2024 22:05:01 -0600 Subject: [PATCH] Explain why the 1.4 package is installed despite the 1.2 compat entry --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7d8d049..18b3946 100644 --- a/README.md +++ b/README.md @@ -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