# Compatibility entry for julia itself is ignored

**URL:** <https://discourse.julialang.org/t/compatibility-entry-for-julia-itself-is-ignored/61309>\
**Category:** General Usage\
**Created:** [May 17, 2021, 4:33pm UTC](https://discourse.julialang.org/t/compatibility-entry-for-julia-itself-is-ignored/61309 "2021-05-17T16:33:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [May 17, 2021, 4:33pm UTC](https://discourse.julialang.org/t/compatibility-entry-for-julia-itself-is-ignored/61309/1 "2021-05-17T16:33:38Z")

</div>

I ran package activation and instantiation for a package that specified julia 1.5.4 in julia 1.6.0. I used the specifier `julia = "~1.5.4"`, which I believe allows only the patch number to vary. However, there was no error or warning.

---

<div class="post-metadata">

**Author:** ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)\
**Post date:** [May 17, 2021, 4:54pm UTC](https://discourse.julialang.org/t/compatibility-entry-for-julia-itself-is-ignored/61309/2 "2021-05-17T16:54:15Z")

</div>

I did this:

```julia-repl
(@v1.6) pkg> generate .julia/dev/TestPkg
  Generating project TestPkg:
    .julia/dev\TestPkg\Project.toml
    .julia/dev\TestPkg\src/TestPkg.jl

```

Then I touched `Project.toml` adding:

```nohighlight
[compat]
julia = "~1.5.4"

```

And then:

```julia-repl
(@v1.6) pkg> dev TestPkg
Path `D:\.julia\dev\TestPkg` exists and looks like the correct package. Using existing path.
   Resolving package versions...
julia version requirement for package `TestPkg [5db33cc8]` not satisfied
...

```

So I did get the warning - although no error, and it did add the package to the Project.toml of the current environment.

If I understand it correctly, the `[compat]` section is taken into account when `add`-ing or `develop`-ing packages, not when activating project environments - there it is the `Manifest.toml` what is used to deal with package versions.

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [May 17, 2021, 7:28pm UTC](https://discourse.julialang.org/t/compatibility-entry-for-julia-itself-is-ignored/61309/3 "2021-05-17T19:28:47Z")

</div>

Right, but what if I want the compatibility checked when I activate/instantiate a project?