# Documenter.jl not updating link to stable releases

**URL:** <https://discourse.julialang.org/t/documenter-jl-not-updating-link-to-stable-releases/97729>\
**Category:** Package Management\
**Created:** [April 21, 2023, 2:02am UTC](https://discourse.julialang.org/t/documenter-jl-not-updating-link-to-stable-releases/97729 "2023-04-21T02:02:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tlnagy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tlnagy/32/5815_2.png) [@tlnagy](https://discourse.julialang.org/u/tlnagy)\
**Post date:** [April 21, 2023, 2:02am UTC](https://discourse.julialang.org/t/documenter-jl-not-updating-link-to-stable-releases/97729/1 "2023-04-21T02:02:15Z")

</div>

Not sure what I’m doing wrong but the links for the “stable” release of [Crispulator.jl](https://github.com/tlnagy/Crispulator.jl) keeps pointing to an old version. The dev version is properly updated, but the stable link is still the old one.

Here’s my [TagBot.yml](https://github.com/tlnagy/Crispulator.jl/blob/4fa322f713ca856200bbc8743c37c192dfd838cf/.github/workflows/TagBot.yml) and my deployment log from Documenter.jl:

```julia
 Info: Deployment criteria for deploying devbranch build from GitHub Actions:
│ - ✔ ENV["GITHUB_REPOSITORY"]="tlnagy/Crispulator.jl" occurs in repo="github.com/tlnagy/Crispulator.jl.git"
│ - ✔ ENV["GITHUB_EVENT_NAME"]="push" is "push", "workflow_dispatch" or "schedule"
│ - ✔ ENV["GITHUB_REF"] matches devbranch="master"
│ - ✔ ENV["GITHUB_ACTOR"] exists and is non-empty
│ - ✔ ENV["GITHUB_TOKEN"] exists and is non-empty
└ Deploying: ✔
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: git branch -m <name>
Initialized empty Git repository in /tmp/jl_LX8U5A/.git/
From https://github.com/tlnagy/Crispulator.jl
 * [new branch] gh-pages -> upstream/gh-pages
 * [new branch] master -> upstream/master
 * [new tag] v0.1 -> v0.1
 * [new tag] v0.2.0 -> v0.2.0
 * [new tag] v0.3.0 -> v0.3.0
 * [new tag] v0.3.1 -> v0.3.1
 * [new tag] v0.3.2 -> v0.3.2
 * [new tag] v0.4.0 -> v0.4.0
 * [new tag] v0.4.1 -> v0.4.1
Switched to a new branch 'gh-pages'
branch 'gh-pages' set up to track 'upstream/gh-pages'.
....
┌ Warning: removing `stable` and linking `stable` to `v0.3.1`.
└ @ Documenter ~/.julia/packages/Documenter/H5y27/src/Documenter.jl:800
┌ Warning: removing `v0.3` and linking `v0.3` to `v0.3.1`.
└ @ Documenter ~/.julia/packages/Documenter/H5y27/src/Documenter.jl:800
┌ Warning: removing `v0.1.0` and linking `v0.1.0` to `v0.1`.
└ @ Documenter ~/.julia/packages/Documenter/H5y27/src/Documenter.jl:800
[gh-pages 37bdcd8] build based on 4fa322f
 12 files changed, 19369 insertions(+), 18424 deletions(-)

```

It doesn’t appear to be detecting version v0.4 or v0.4.1 or v0.5.

Any suggestions on what to try?

---

<div class="post-metadata">

**Author:** ![odow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/odow/32/28685_2.png) [@odow](https://discourse.julialang.org/u/odow)\
**Post date:** [April 21, 2023, 3:31am UTC](https://discourse.julialang.org/t/documenter-jl-not-updating-link-to-stable-releases/97729/2 "2023-04-21T03:31:32Z")

</div>

See [Fix when CI runs by odow · Pull Request #61 · tlnagy/Crispulator.jl · GitHub](https://github.com/tlnagy/Crispulator.jl/pull/61)

---

<div class="post-metadata">

**Author:** ![tlnagy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tlnagy/32/5815_2.png) [@tlnagy](https://discourse.julialang.org/u/tlnagy)\
**Post date:** [April 25, 2023, 10:02pm UTC](https://discourse.julialang.org/t/documenter-jl-not-updating-link-to-stable-releases/97729/3 "2023-04-25T22:02:39Z")

</div>

Okay so this is interesting. Made a separate tag + @odow’s patch = Documenter built the docs. But now that I released a new version, the CI skipped again. Not sure what is going on.