# Github action fails for documentation

**URL:** https://discourse.julialang.org/t/github-action-fails-for-documentation/137313
**Category:** New to Julia
**Tags:** github, ci-workflow
**Created:** [May 28, 2026, 11:45am UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313 "2026-05-28T11:45:33Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Boris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/boris/32/3306_2.png) [@Boris](https://discourse.julialang.org/u/Boris)
#### Post date: [May 28, 2026, 11:45am UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/1 "2026-05-28T11:45:34Z")

</div>

Hi. I have a package on github and a CI worklfow for the documentation. I haven’t done any commits in a while and last time everything was working. Today the documentation build on github fails with a somewhat werid error:

```julia
Run using Pkg
  using Pkg
  Pkg.develop(PackageSpec(path=pwd()))
  Pkg.instantiate()
  shell: /opt/hostedtoolcache/julia/1.12.6/x64/bin/julia --color=yes --project=docs {0}
  Installing known registries into `~/.julia`
       Added `General` registry to ~/.julia/registries
    Updating registry at `~/.julia/registries/General.toml`
   Resolving package versions...
ERROR: LoadError: version 6.10.2+1 of package Qt6Base_jll is not available. Available versions: 6.0.3+0, 6.0.3+1, 6.3.0+0, 6.3.0+1, 6.4.1+0, 6.4.1+1, 6.4.2+0, 6.4.2+1, 6.4.2+2, 6.4.2+3, 6.5.2+0, 6.5.2+1, 6.5.2+2, 6.5.3+0, 6.5.3+1, 6.7.0+0, 6.7.0+1, 6.7.1+0, 6.7.1+1, 6.8.1+0, 6.8.2+0, 6.8.2+1, 6.8.2+2, 6.10.2+2
Stacktrace:
  [1] pkgerror(msg::String)
    @ Pkg.Types /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Types.jl:68
  [2] resolve_versions!(env::Pkg.Types.EnvCache, registries::Vector{Pkg.Registry.RegistryInstance}, pkgs::Vector{PackageSpec}, julia_version::VersionNumber, installed_only::Bool)
    @ Pkg.Operations /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:614
  [3] targeted_resolve
    @ /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1754 [inlined]
  [4] tiered_resolve(env::Pkg.Types.EnvCache, registries::Vector{Pkg.Registry.RegistryInstance}, pkgs::Vector{PackageSpec}, julia_version::VersionNumber, try_all_installed::Bool)
    @ Pkg.Operations /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1726
  [5] _resolve(io::IOContext{IO}, env::Pkg.Types.EnvCache, registries::Vector{Pkg.Registry.RegistryInstance}, pkgs::Vector{PackageSpec}, preserve::PreserveLevel, julia_version::VersionNumber)
    @ Pkg.Operations /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1766
  [6] develop(ctx::Pkg.Types.Context, pkgs::Vector{PackageSpec}, new_git::Set{Base.UUID}; preserve::PreserveLevel, platform::Base.BinaryPlatforms.Platform)
    @ Pkg.Operations /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1850
  [7] develop
    @ /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1839 [inlined]
  [8] develop(ctx::Pkg.Types.Context, pkgs::Vector{PackageSpec}; shared::Bool, preserve::PreserveLevel, platform::Base.BinaryPlatforms.Platform, kwargs::@Kwargs{io::IOContext{IO}})
    @ Pkg.API /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/API.jl:294
  [9] develop(pkgs::Vector{PackageSpec}; io::IOContext{IO}, kwargs::@Kwargs{})
    @ Pkg.API /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/API.jl:169
 [10] develop(pkgs::Vector{PackageSpec})
    @ Pkg.API /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/API.jl:158
 [11] develop(pkg::PackageSpec)
    @ Pkg.API /opt/hostedtoolcache/julia/1.12.6/x64/share/julia/stdlib/v1.12/Pkg/src/API.jl:156
 [12] top-level scope
    @ ~/work/_temp/22c679c3-8f03-4930-b8eb-bc1f7d2ae4af:2
 [13] include(mod::Module, _path::String)
    @ Base ./Base.jl:306
 [14] exec_options(opts::Base.JLOptions)
    @ Base ./client.jl:317
 [15] _start()
    @ Base ./client.jl:550
in expression starting at /home/runner/work/_temp/22c679c3-8f03-4930-b8eb-bc1f7d2ae4af:2
Error: Process completed with exit code 1.

```

I don’t think I have done or changed anything. Any ideas what this could be? I don’t know if the actions are visible, but the repo is public: [GitHub - borisblagov/BEAVARs.jl: Early version of a personal package of mine for estimating Bayesian VAR models · GitHub](https://github.com/borisblagov/BEAVARs.jl)

---

<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: [May 28, 2026, 11:52am UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/2 "2026-05-28T11:52:10Z")

</div>

Do you actually need to [check in the manifest](https://github.com/borisblagov/BEAVARs.jl/blob/dc534c6f0c8c0007b667d08bc63cf6efa28669c4/docs/Manifest.toml)? If so, re-resolve it, [Qt6Base\_jll v6.10.2+1 was yanked](https://github.com/JuliaRegistries/General/pull/155133), if not just delete it and live happy.

---

<div class="post-metadata">

### Author: ![Boris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/boris/32/3306_2.png) [@Boris](https://discourse.julialang.org/u/Boris)
#### Post date: [May 28, 2026, 12:12pm UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/3 "2026-05-28T12:12:28Z")

</div>

What do you mean by checking the manifest? Is my configuration wrong? Sorry, I am not sure what I am doing, I have mostly, blindly followed [thi guide for hosting github pages documentation](https://m3g.github.io/JuliaNotes.jl/stable/publish_docs/#Create-an-empty-gh-pages-branch-and-choose-it-to-deploy-the-page) and so far it has worked without issues.

I tried updating the packages and `resolve` does not bring any issues, says no packages to add or remove from the manifest.

Is there a way to make it use Qt6Base\_jll 6.10.2+2? I don’t even know what package installed it. I guess manually editing the line `version = "6.10.2+1` in the Manifest is not a good idea?

Edit:  
when I try

```julia
BEAVARs) pkg> rm Qt6Base_jll
ERROR: The following package names could not be resolved:
 * Qt6Base_jll (c0090381-4147-56d7-9ebc-da0b1113ec56 in manifest but not in project)

```

but

```julia
(BEAVARs) pkg> resolve
     Project No packages added to or removed from `...\BEAVARs\Project.toml`
    Manifest No packages added to or removed from `...\BEAVARs\Project.toml`

```

Is there a way to make the project and manifest consistent and clean all the unneded dependencies?

Edit2: I am an idiot, I should be updating/resolving the Manifest in docs, not the main one, duh  
resolving did not do the trick but updating the docs environment fixed it, thanks!

---

<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: [May 28, 2026, 1:19pm UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/4 "2026-05-28T13:19:37Z")

</div>

> [@Boris](#):
>
> What do you mean by checking the manifest?

To “check in” a file to a git repository [it means](https://stackoverflow.com/q/47874778) to track it, so that its content is inside the repository, and following changes are tracked.

> [@Boris](#):
>
> I should be updating/resolving the Manifest in docs

That’s the file I linked above 🙂

But my point is: do you even need the manifest to start with? I personally never check in manifests for packages, I instead use them for “applications” where I specifically don’t want to change the environment.

---

<div class="post-metadata">

### Author: ![Boris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/boris/32/3306_2.png) [@Boris](https://discourse.julialang.org/u/Boris)
#### Post date: [May 29, 2026, 8:35am UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/5 "2026-05-29T08:35:15Z")

</div>

Tbh, I probably don’t.

I just never thought about adding it to the gitignore. That should prevent such problems in the future, should it not?

---

<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: [May 29, 2026, 8:41am UTC](https://discourse.julialang.org/t/github-action-fails-for-documentation/137313/6 "2026-05-29T08:41:02Z")

</div>

> [@Boris](#):
>
> That should prevent such problems in the future

That’s my point (and manifests in package development are more often than not a hassle)
