Downloads of v 0.19.0:


Last Update:

01 Mar 2017

Package Maintainer(s):

Software Author(s):

  • spf13


hugo admin blog website network


This is not the latest version of hugo available.

  • 1
  • 2
  • 3

0.19.0 | Updated: 01 Mar 2017



Downloads of v 0.19.0:



Software Author(s):

  • spf13

  • 1
  • 2
  • 3
hugo 0.19.0

This is not the latest version of hugo available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install hugo, run the following command from the command line or from PowerShell:


To upgrade hugo, run the following command from the command line or from PowerShell:


To uninstall hugo, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade hugo -y --source="'INTERNAL REPO URL'" --version="'0.19.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade hugo -y --source="'INTERNAL REPO URL'" --version="'0.19.0'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install hugo
    name: hugo
    version: '0.19.0'
    state: present

See docs at

chocolatey_package 'hugo' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.19.0'

See docs at

cChocoPackageInstaller hugo
    Name     = "hugo"
    Version  = "0.19.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'hugo':
  ensure   => '0.19.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 05 Apr 2017.



A Fast and Flexible Static Site Generator built with love by spf13 and friends in Go.

Website |
Forum |
Developer Chat (no support) |
Documentation |
Installation Guide |
Contribution Guide |

Linux and OS X Build Status
Windows Build Status
Dev chat at
Go Report Card


Hugo is a static HTML and CSS website generator written in [Go][].
It is optimized for speed, easy use and configurability.
Hugo takes a directory with content and templates and renders them into a full HTML website.

Hugo relies on Markdown files with front matter for meta data.
And you can run Hugo from any directory.
This works well for shared hosts and other systems where you don’t have a privileged account.

Hugo renders a typical website of moderate size in a fraction of a second.
A good rule of thumb is that each piece of content renders in around 1 millisecond.

Hugo is designed to work well for any kind of website including blogs, tumbles and docs.

Contributing to Hugo

We welcome contributions to Hugo of any kind including documentation, themes,
organization, tutorials, blog posts, bug reports, issues, feature requests,
feature implementations, pull requests, answering questions on the forum,
helping to manage issues, etc.

The Hugo community and maintainers are very active and helpful, and the project benefits greatly from this activity.

Asking Support Questions

We have an active discussion forum where users and developers can ask questions.
Please don't use the Github issue tracker to ask questions.

Reporting Issues

If you believe you have found a defect in Hugo or its documentation, use
the Github issue tracker to report the problem to the Hugo maintainers.
If you're not sure if it's a bug or not, start by asking in the discussion forum.
When reporting the issue, please provide the version of Hugo in use (hugo version).


$ErrorActionPreference = 'Stop'; # stop on all errors
Install-ChocolateyZipPackage -packageName 'hugo' -UnzipLocation $(Split-Path -Parent $MyInvocation.MyCommand.Definition) -Url '' -checksum 'FA2660049E9DF0A75C8EC03CEBCB4D4A696579E1F111635BE7355549DBA011A0' -checksumType 'sha256'-Url64 '' -checksum64 '36DB6333346025C688F18F525C720C9B1BB4D9E5329E4A48F4BC507B033EE9B7' -checksumType64 'sha256'

$hugoExe = Get-ChildItem $(Split-Path -Parent $MyInvocation.MyCommand.Definition) | Where-Object -Property Name -Match "hugo_[\d\.]+_windows_(386|amd64)\.exe"

if (-Not($hugoExe)) 
    Write-Error -Message "hugo exe is not found, please contact the maintainer of the package" -Category ResourceUnavailable
elseif ($hugoExe.Count -lt 1) 
    Write-Error -Message "more than one hugo exe found, please contact the maintainer of the package" -Category ResourceUnavailable

Write-Host "found hugo exe in $($hugoExe.FullName)"
Write-Host "attempting to rename it to hugo.exe" 
Rename-Item -Path $hugoExe.FullName -NewName hugo.exe

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Hugo 0.92.0 1536 Wednesday, January 12, 2022 Approved
Hugo 0.91.2 1707 Thursday, December 23, 2021 Approved
Hugo 0.91.1 176 Wednesday, December 22, 2021 Approved
Hugo 0.91.0 15 Friday, December 17, 2021 Approved
Hugo 0.90.1 1267 Friday, December 10, 2021 Approved
Hugo 0.90.0 320 Wednesday, December 8, 2021 Approved
Hugo 0.89.4 1885 Wednesday, November 17, 2021 Approved
Hugo 0.89.3 337 Monday, November 15, 2021 Approved
Hugo 0.89.2 789 Monday, November 8, 2021 Approved

0.19 February 27th 2017

We’re happy to announce the first release of Hugo in 2017.

This release represents over 180 contributions by over 50 contributors to the main Hugo code base. Since last release Hugo has gained 1450 stars, 35 new contributors and 15 additional themes.

Hugo now has:

  • 15200+ stars
  • 470+ contributors
  • 151+ themes

Furthermore, Hugo has its own Twitter account (@gohugoio) where we share bite-sized news and themes from the Hugo community.

@bep leads the Hugo development and once again contributed a significant amount of additions. Also a big shoutout to @chaseadamsio for the Emacs Org-mode support, @digitalcraftsman for his relentless work on keeping the documentation and the themes site in pristine condition, @fj for his work on revising the params handling in Hugo, and @moorereason and @bogem for their ongoing contributions.


Hugo 0.19 brings native Emacs Org-mode content support ( #1483 ), big thanks to @chaseadamsio.

Also, a considerably amount of work have been put into cleaning up the Hugo source code, in an issue titled Refactor the globals out of site build. This is not immediately visible to the Hugo end user, but will speed up future development.

Hugo 0.18 was bringing full-parallel page rendering, so workarounds depending on rendering order did not work anymore, and pages with duplicate target paths (common examples would be / or /about/ would now conflict with the home page or the section listing.

With Hugo 0.19, you can control this behaviour by turning off page types you do not want ( #2534 ). In its most extreme case, if you put the below setting in your config.toml, you will get nothing!:

disableKinds = ["page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"]

Other New Features

  • Add ability to sort pages by frontmatter parameters, enabling easy custom “top 10” page lists. #3022
  • Add truncate template function #2882
  • Add now function, which replaces the now deprecated .Now #2882
  • Make RSS item limit configurable #3035


  • Enhance .Param to permit arbitrarily nested parameter references #2598
  • Use Page.Params more consistently when adding metadata #3033
  • The sectionPagesMenu feature (“Section menu for the lazy blogger”) is now integrated with the section content pages. #2974
  • Hugo 0.19 is compiled with Go 1.8!
  • Make template funcs like findRE and friends more liberal in what argument types they accept #3018 #2822
  • Improve generation of OpenGraph date tags #2979


  • sourceRelativeLinks is now deprecated and will be removed in Hugo 0.21 if no one is stepping up to the plate and fixes and maintains this feature. #3028


  • Fix .Site.LastChange on sites where the default sort order is not chronological. #2909
  • Fix regression of .Truncated evaluation in manual summaries. #2989
  • Fix preserveTaxonomyNames regression #3070
  • Fix issue with taxonomies when only some have content page #2992
  • Fix instagram shortcode panic on invalid ID #3048
  • Fix subtle data race in getJSON #3045
  • Fix deadlock in cached partials #2935
  • Avoid double-encoding of paginator URLs #2177
  • Allow tilde in URLs #2177
  • Fix .Site.Pages handling on live reloads #2869
  • UniqueID now correctly uses the fill file path from the content root to calculate the hash, and is finally … unique!
  • Discard current language based on .Lang(), go get translations correct for paginated pages. #2972
  • Fix infinite loop in template AST handling for recursive templates #2927
  • Fix issue with watching when config loading fails #2603
  • Correctly flush the imageConfig on live-reload #3016
  • Fix parsing of TOML arrays in frontmatter #2752


  • Add tutorial “How to use Google Firebase to host a Hugo site” #3007
  • Improve documentation for menu rendering #3056
  • Revise GitHub Pages deployment tutorial #2930

This package has no dependencies.

Discussion for the hugo Package

Ground Rules:

  • This discussion is only about hugo and the hugo package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or hugo, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus