# Error when building documentation with github actions

**URL:** https://discourse.julialang.org/t/error-when-building-documentation-with-github-actions/56139
**Category:** Package Management
**Tags:** documentation, ci
**Created:** [February 27, 2021, 12:42pm UTC](https://discourse.julialang.org/t/error-when-building-documentation-with-github-actions/56139 "2021-02-27T12:42:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Azzaare](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/azzaare/32/21008_2.png) [@Azzaare](https://discourse.julialang.org/u/Azzaare)
#### Post date: [February 27, 2021, 12:42pm UTC](https://discourse.julialang.org/t/error-when-building-documentation-with-github-actions/56139/1 "2021-02-27T12:42:39Z")

</div>

I’ve just generated a new package and put it on GitHub [COPInstances.jl](https://github.com/JuliaConstraints/COPInstances.jl)  
I get the following error while building the documentation. Which is odd as I have the same setup for other packages (beside not being registered yet).

```julia
ERROR: could not find entry with uuid fa267f1f-6049-4f14-aa54-33bafae1ed76 in manifest /home/runner/work/COPInstances.jl/COPInstances.jl/docs/Manifest.toml

```

The uuid refer to `TOML.jl`, but it is a registered package that seems compatible with any `v1` of julia …

Any idea of what is happening and why?

---

<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: [February 27, 2021, 1:25pm UTC](https://discourse.julialang.org/t/error-when-building-documentation-with-github-actions/56139/2 "2021-02-27T13:25:43Z")

</div>

Delete `docs/Manifest.toml` and remove your package from `docs/Project.toml`.

About the why: you probably created the manifest with julia v1.6, but then you’re building the documentation in GitHub Actions with julia v1.5, but manifests are julia-version-specific and the presence of TOML (a stdlib in v1.6 but not v1.5 confuses the resolver). Having the manifest in CI is a bad idea, unless you consistently use the same version of Julia to generate it and instantiate the environment.

Regarding why removing your package from `docs/Project.toml`: your package will be `dev`’ed when building the documentation, but it should _not_ be in the committed Project.toml.

---

<div class="post-metadata">

### Author: ![Azzaare](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/azzaare/32/21008_2.png) [@Azzaare](https://discourse.julialang.org/u/Azzaare)
#### Post date: [February 27, 2021, 2:31pm UTC](https://discourse.julialang.org/t/error-when-building-documentation-with-github-actions/56139/3 "2021-02-27T14:31:37Z")

</div>

Thank you so much!

I used `PkgTemplates` and for some reasons I assumed there would be no manifest for docs (since I chose an option for no manifest), but it doesn’t seem to be the case.

Thank you for the explanation, it does make sense, so I will remember it for next package ^^
