# loadError on MbedTLS\_jll

**URL:** <https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969>\
**Category:** Package Management\
**Tags:** question, package\
**Created:** [October 8, 2025, 9:33am UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969 "2025-10-08T09:33:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dankelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dankelley/32/33539_2.png) [@dankelley](https://discourse.julialang.org/u/dankelley)\
**Post date:** [October 8, 2025, 9:33am UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969/1 "2025-10-08T09:33:05Z")

</div>

I have a package ([GitHub - dankelley/OceanAnalysis.jl: Julia code for oceanographic analysis](http://github.com/dankelley/OceanAnalysis.jl)) that did the github workflow “Documentation” yesterday (12 hours ago), but not today, after I change a README file.

So I undid my minor changes, so that now I have a version (commit d5906606d500da26ff98a1486e055020dbec2894) that is identical to yesterday’s version (commit 3b7dc099566b2ba9bdf800a24bf2be82f8775428).

I would have expected that if the GH action worked yesterday, then it would work today as well. That’s not the case, though, and that’s why I am posting this.

**More information**

The GH action output says

```julia-auto
Warning: The active manifest file has dependencies that were resolved with a different julia version (1.11.7). Unexpected behavior may occur.

```

I have 1.11.7 on my machine … maybe I need to change to another version? Maybe the github testing machine is updated to 1.11.8, or a bit older at 1.11.6? But this is just a warning – it’s not my main concern.

Rather, the main concern is the error that’s reported a few lines after that warning. It says

```julia-auto
ERROR: LoadError: Failed to find path for package MbedTLS_jll

```

I don’t have a `using` on that package but I guess it’s drawn in by something else that I’ve used. I am still confused on what things are set at what levels. I guess I could wipe out my `~/.julia` stuff and try again, but this seems to be a strong measure given that the github action worked properly just 12h ago, on identical source code.

Any thoughts?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [October 8, 2025, 9:59am UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969/2 "2025-10-08T09:59:45Z")

</div>

Julia v1.12 was released in the last few hours.

> [@dankelley](#):
>
> ```julia-auto
> Warning: The active manifest file has dependencies that were resolved with a different julia version (1.11.7). Unexpected behavior may occur.
> 
> ```

Do you have a checked in manifest in your repo? Any specific reason for doing it?

---

<div class="post-metadata">

**Author:** ![dankelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dankelley/32/33539_2.png) [@dankelley](https://discourse.julialang.org/u/dankelley)\
**Post date:** [October 8, 2025, 10:02am UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969/3 "2025-10-08T10:02:14Z")

</div>

Oh, yes, I do have a checked-in Manifest.toml. I also have a checked-in Project.toml file. Should I remove both from the repo?

Also, thanks for the note on the update to Julia.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [October 8, 2025, 10:04am UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969/4 "2025-10-08T10:04:18Z")

</div>

> [@dankelley](#):
>
> Oh, yes, I do have a checked-in Manifest.toml. I also have a checked-in Project.toml file. Should I remove both from the repo?

The Project file not really, that’s quite important. It depends on what you’re using it for specifically (that’s why I asked), but only for testing regular packages I’d recommend not checking in the Manifest and let the package manager resolve the environment. Manifests are very version-dependent, so when you upgrade Julia to a newer minor versions they aren’t useful anymore (hence the warning). Manifests are useful for reproduction of an application/pipeline which is running with a fixed version of Julia.

---

<div class="post-metadata">

**Author:** ![dankelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dankelley/32/33539_2.png) [@dankelley](https://discourse.julialang.org/u/dankelley)\
**Post date:** [October 8, 2025, 12:24pm UTC](https://discourse.julialang.org/t/loaderror-on-mbedtls-jll/132969/5 "2025-10-08T12:24:48Z")

</div>

This is very informative. I’ve taken the `Manifest.toml` out of the repo. I’ve also updated my version of Julia. Thanks again!!