Skip to content

Explain why the 1.4 package is installed despite the 1.2 compat entry #8

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Explain why the 1.4 package is installed despite the 1.2 compat entry #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
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