# Hugo 0.48 Released

**URL:** <https://discourse.gohugo.io/t/hugo-0-48-released/13908>\
**Category:** Announcements\
**Created:** [August 29, 2018, 8:12am UTC](https://discourse.gohugo.io/t/hugo-0-48-released/13908 "2018-08-29T08:12:51Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![anthonyfok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/anthonyfok/32/106_2.png) [@anthonyfok](https://discourse.gohugo.io/u/anthonyfok)\
**Post date:** [September 3, 2018, 1:40pm UTC](https://discourse.gohugo.io/t/hugo-0-48-released/13908/12 "2018-09-03T13:40:51Z")

</div>

> [@bep](#):
>
> Note that you can get the same behaviour by making sure Hugo is built outside of GOPATH (see the current Appveyor YAML).

Thanks! I didn’t know that, as I haven’t yet to try out Go 1.11. \<grin, duck, run\>

For snapcraft.yaml, I am taking the easy way out by setting GO111MODULE within the override-build script, alongside where GOPATH and PATH were set: [snapcraft: Set GO111MODULE=on in override-build script · gohugoio/hugo@3ddbb7f · GitHub](https://github.com/gohugoio/hugo/commit/3ddbb7f) (testing it on the extended-snap-master first before pushing the change to master and stable branches)

Update: Nope, setting GO111MODULE=on globally didn’t work. Strange errors with other Go packages. I’d better follow your example in .travis.yml by applying `env GO111MODULE=on` to the `go get github.com/magefile/mage` command only.

Update 2: Nope, that didn’t work either. That means I really should look at your latest changes to Appveyor YAML and [https://github.com/magefile/mage/issues/79](https://github.com/magefile/mage/issues/79) carefully. Haha, not as simple as I had thought!

---

_[View the full topic](https://discourse.gohugo.io/t/hugo-0-48-released/13908)._