# Versioning of documentation fails

**URL:** <https://discourse.julialang.org/t/versioning-of-documentation-fails/42795>\
**Category:** General Usage\
**Tags:** documenter\
**Created:** [July 9, 2020, 6:22pm UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795 "2020-07-09T18:22:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lgo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lgo/32/48751_2.png) [@lgo](https://discourse.julialang.org/u/lgo)\
**Post date:** [July 9, 2020, 6:22pm UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795/1 "2020-07-09T18:22:41Z")

</div>

I’m trying to achieve versioning for my documentation created with documenter. I’ve set the `devbranch = "dev"` in the `deploydocs` function, but use the defaults apart from that. Yet still, in the documenation the dropdown menu only shows the option `dev`, even after I changed my version (e.g. from 0.8.29 to 0.8.3). Also, the gh-pages branch does not show any versions apart from `dev`.

I’ve compared this with the setups of other documenations that achieve versioning and did not find a difference. Travis does not report any errors.

---

<div class="post-metadata">

**Author:** ![mortenpi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mortenpi/32/158_2.png) [@mortenpi](https://discourse.julialang.org/u/mortenpi)\
**Post date:** [July 9, 2020, 9:56pm UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795/2 "2020-07-09T21:56:05Z")

</div>

Did Travis actually run for the _tag_? It can happen that branch settings in `.travis.yml` disallow it. Could you provide links to the configuration and Travis logs?

---

<div class="post-metadata">

**Author:** ![lgo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lgo/32/48751_2.png) [@lgo](https://discourse.julialang.org/u/lgo)\
**Post date:** [July 10, 2020, 6:43am UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795/3 "2020-07-10T06:43:16Z")

</div>

Here are links to the travis [configuration](https://github.com/leonardgoeke/anyMOD.jl/blob/dev/.travis.yml) and [logs](https://api.travis-ci.org/v3/job/706619564/log.txt).

---

<div class="post-metadata">

**Author:** ![mortenpi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mortenpi/32/158_2.png) [@mortenpi](https://discourse.julialang.org/u/mortenpi)\
**Post date:** [July 10, 2020, 8:49am UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795/4 "2020-07-10T08:49:13Z")

</div>

It looks like you haven’t created a [tag/release](https://github.com/leonardgoeke/anyMOD.jl/releases) corresponding to the release (with the version number as the tag). It should be sufficient if you just create a tag in the GitHub interface, to get the documentation to deploy.

However, it also looks like you haven’t registered you package in the [General registry](https://github.com/JuliaRegistries/General) yet? Just be aware that you need to do that in order to get “proper” releases (that you can simply `pkg> add` without the URL). Once you decide to do that, you probably want to set up [TagBot](https://github.com/JuliaRegistries/TagBot), which can create the tags automatically for you.

---

<div class="post-metadata">

**Author:** ![lgo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lgo/32/48751_2.png) [@lgo](https://discourse.julialang.org/u/lgo)\
**Post date:** [July 11, 2020, 12:27pm UTC](https://discourse.julialang.org/t/versioning-of-documentation-fails/42795/5 "2020-07-11T12:27:04Z")

</div>

Thanks. I was not aware of that.