Downloads of v 0.43:


Last Update:

14 Jul 2018

Package Maintainer(s):

Software Author(s):

  • spf13


hugo admin blog website network


This is not the latest version of hugo available.

0.43 | Updated: 14 Jul 2018



Downloads of v 0.43:



Software Author(s):

  • spf13

hugo 0.43

This is not the latest version of hugo available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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:


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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade hugo -y --source="'STEP 3 URL'" [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="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure hugo installed
    name: hugo
    state: present
    version: 0.43
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'hugo' do
  action    :install
  version  '0.43'
  source   'STEP 3 URL'

See docs at

    Name: hugo,
    Version: 0.43,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller hugo
   Name     = 'hugo'
   Ensure   = 'Present'
   Version  = '0.43'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'hugo':
  provider => 'chocolatey',
  ensure   => '0.43',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install hugo version="0.43" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 14 Jul 2018.



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'

$packageName= $env:ChocolateyPackageName
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = "$($env:ChocolateyPackageVersion)/hugo_$($env:ChocolateyPackageVersion)"
$url64      = "$($env:ChocolateyPackageVersion)/hugo_$($env:ChocolateyPackageVersion)"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $url
  url64bit      = $url64

  checksum      = '5e5da00419ef280557a7cb6e84483fca7515dc7712a8bfe892d790d472e83eef'
  checksumType  = 'sha256'
  checksum64    = '907d0922488e40039a7078a89b83e9fa70312e3d6610a4067f491a629f46b315'
  checksumType64= 'sha256'

Install-ChocolateyZipPackage @packageArgs
$ErrorActionPreference = 'Stop';

$hugoExe = Get-ChildItem $(Split-Path -Parent $MyInvocation.MyCommand.Definition) | Where-Object -Property Name -Match "hugo.exe"

if (-Not($hugoExe)) 
    Write-Error -Message "hugo exe is not found, please contact the maintainer of the package" -Category ResourceUnavailable

Write-Host "found hugo exe in $($hugoExe.FullName)"
Write-Host "attempting to remove it" 
Remove-Item $hugoExe.FullName

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.

Version Downloads Last Updated Status
Hugo 0.76.4 661 Monday, October 12, 2020 Approved
Hugo 0.76.3 550 Thursday, October 8, 2020 Approved
Hugo 0.76.2 305 Wednesday, October 7, 2020 Approved
Hugo 0.76.0 152 Tuesday, October 6, 2020 Approved
Hugo 0.75.1 2061 Tuesday, September 15, 2020 Approved
Hugo 0.75.0 240 Monday, September 14, 2020 Approved
Hugo 0.74.3 3943 Thursday, July 23, 2020 Approved
Hugo 0.74.2 754 Friday, July 17, 2020 Approved
Hugo 0.74.1 574 Tuesday, July 14, 2020 Approved

**0.43 ** July 8th 2018


  • Replace deprecated {Get,}ByPrefix with {Get,}Match 42ed6025 @anthonyfok
  • Hugo is now released with two binary version: One with and one without SCSS/SASS support. At the time of writing, this is only available in the binaries on the GitHub release page. Brew, Snap builds etc. will come. But note that you only need the extended version if you want to edit SCSS. For your CI server, or if you don't use SCSS, you will most likely want the non-extended version.



  • Return en empty slice in after instead of error f8212d20 @bep #4894
  • Update internal pagination template to support Bootstrap 4 ca1e46ef @bep #4881
  • Support text/template/parse API change in go1.11 9f27091e @anthonyfok #4784


  • Allow forward slash in shortcode names de37455e @bep #4886
  • Reset the global pages cache on server rebuilds 128f14ef @bep #4845


  • Bump CircleCI image e3df6478 @bep
  • Add Goreleaser extended config 626afc98 @bep #4908
  • Build both hugo and hugo.extended for 0.43 e1027c58 @anthonyfok #4908
  • Add temporary build script bfc3488b @bep
  • Add "extended" to "hugo version" ce84b524 @anthonyfok #4913
  • Add a newScratch template func 2b8d907a @bep #4685
  • Add Hugo Piper with SCSS support and much more dea71670 @bep #4381#4903#4858
  • Consider root and current section's content type if set in front matter c790029e @bep #4891
  • Update docker image 554553c0 @bep
  • Merge branch 'release-0.42.2' 282f6035 @bep
  • Release 0.42.2 1637d12e @bep
  • Update GoReleaser config 1f0c4e1f @caarlos0
  • Create missing head.html partial on new theme generation fd71fa89 @openscript
  • Add html doctype to baseof.html template for new themes b5a3aa70 @openscript
  • Adds .gitattributes to force Go files to LF 6a2968fd @neurocline
  • Update to Go 1.9.7 and Go 1.10.3 23d5fc82 @anthonyfok
  • Update Dockerfile to a multi-stage build 8531ec7c @skoblenick #4154
  • Release 0.42.1 d67e843c @bep
  • Do not fail server build when /static is missing 34ee27a7 @bep #4846


  • Do not create paginator pages for the other output formats 43338c3a @bep #4890
  • Fix the shortcodes/partials vs base template detection a5d0a57e @bep #4897
  • nfpm replacements e1a052ec @caarlos0
  • Fix typos 3cea2932 @idealhack

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