# Docs (by Documenter) are not being updated in gh-pages branch

**URL:** <https://discourse.julialang.org/t/docs-by-documenter-are-not-being-updated-in-gh-pages-branch/19832>\
**Category:** General Usage\
**Created:** [January 20, 2019, 12:57am UTC](https://discourse.julialang.org/t/docs-by-documenter-are-not-being-updated-in-gh-pages-branch/19832 "2019-01-20T00:57:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Gnimuc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gnimuc/32/2194_2.png) [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)\
**Post date:** [January 20, 2019, 3:23am UTC](https://discourse.julialang.org/t/docs-by-documenter-are-not-being-updated-in-gh-pages-branch/19832/2 "2019-01-20T03:23:49Z")

</div>

It looks like the deployment process was skipped: [Travis CI - Test and Deploy with Confidence](https://travis-ci.org/GenericMappingTools/GMT.jl/jobs/481628503#L3560)

Have you considered to upgrade Documenter.jl to 0.20+?

> [@PSA: Documenter.jl breaking changes & version capping](https://discourse.julialang.org/t/psa-documenter-jl-breaking-changes-version-capping/16431):
>
> This is relevant for package developers using [Documenter.jl](https://github.com/JuliaDocs/Documenter.jl) for their package documentation. The upcoming Documenter 0.20 will introduce breaking changes to the way makedocs and deploydocs arguments are interpreted. This means that most existing make.jl scripts have to be updated before they work correctly with the new version. As you might have already noticed, a bunch of METADATA-registered packages just got hit with automated PRs that cap the Documenter version used in Travis to 0.19. Howev…

---

_[View the full topic](https://discourse.julialang.org/t/docs-by-documenter-are-not-being-updated-in-gh-pages-branch/19832)._