# Latest stable documentation not being deployed
**URL:** https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053
**Category:** General Usage
**Tags:** documentation, documenter, tagbot
**Created:** [September 30, 2022, 6:07pm UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053 "2022-09-30T18:07:23Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jishnub](https://discourse.julialang.org/u/jishnub)
#### Post date: [September 30, 2022, 6:07pm UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/1 "2022-09-30T18:07:23Z")
I’m trying to get the stable documentation for `ApproxFun.jl` to build.
The [tagbot script](https://github.com/JuliaApproximation/ApproxFun.jl/blob/master/.github/workflows/TagBot.yml) contains
```julia
ssh: ${{ secrets.DOCUMENTER_KEY }}
```
and the [documentation job script](https://github.com/JuliaApproximation/ApproxFun.jl/blob/master/.github/workflows/docs.yml) contains
```julia
on:
pull_request:
push:
branches:
- 'master'
- 'backport**'
tags: '*'
```
but, for some reason, the documenter job didn’t run on the recently tagged versions. In the past, the SSH secret hadn’t been included, so the documentation wasn’t being built on tags. I added this in `v0.13.8`, and was able to get the documentation to build and deploy correctly by pushing a tag manually. This is available now as [the documentation for v0.13.8](https://juliaapproximation.github.io/ApproxFun.jl/v0.13.8/). However, after that, the documenter job didn’t get triggered when versions v0.13.9 and 0.13.10 were tagged by the tagbot. I just tried pushing an additional tag `v0.13.10-doc1` manually, but even that didn’t trigger the documenter job. I wonder why the job isn’t being triggered on tags?
The secret seems ok, as the documentation for `v0.13.8` did build correctly.
---
### Author:  [@jishnub](https://discourse.julialang.org/u/jishnub)
#### Post date: [October 3, 2022, 7:20am UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/2 "2022-10-03T07:20:27Z")
@fredrikekre sorry to tag you, but I wonder if you might have some insights into what’s happening here?
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [October 3, 2022, 8:19am UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/3 "2022-10-03T08:19:48Z")
Not sure really. Does the key have correct permissions? Note that regular CI didn’t run either on the pushed tag.
---
### Author:  [@cortner](https://discourse.julialang.org/u/cortner)
#### Post date: [July 28, 2023, 3:32pm UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/4 "2023-07-28T15:32:50Z")
@jishnub - I’m in the same situation. what did you do to resolve this? I wondered about separating the doc build from the CI into a separate yml - do the lines
```julia
release:
types: [published]
```
in your package then trigger the doc build?
---
### Author:  [@jishnub](https://discourse.julialang.org/u/jishnub)
#### Post date: [July 28, 2023, 4:23pm UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/5 "2023-07-28T16:23:47Z")
In this case it turned out to be a missing `DOCUMENTER_KEY` on GitHub. Adding the key fixed the issue. At the time of this post, I didn’t have access to the repo keys, which led to the confusion
---
### Author:  [@cortner](https://discourse.julialang.org/u/cortner)
#### Post date: [July 28, 2023, 4:29pm UTC](https://discourse.julialang.org/t/latest-stable-documentation-not-being-deployed/88053/6 "2023-07-28T16:29:36Z")
Thank you