A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/merge_requests/1158 below:

Roll forward version of Hugo forward locally and in new Docker builds (!1158) · Merge requests · GitLab.org / Technical Writing

Skip to content Roll forward version of Hugo forward locally and in new Docker builds What does this MR do and why?

In GitLab CI/CD pipelines, our site is currently compiled with a Docker image that contains a relatively old version of Hugo and a relatively old version of Go.

As we look to keep our versions of Go synchronised with the versions of Go used in other projects at GitLab, using an older Docker image can block MRs like: !1136, with build errors such as: https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/jobs/11026861730.

If we specify a newer version of Hugo for HUGO_VERSION_NEXT, we can create a newer Docker images for site builds that use more up-to-date versions of Hugo and Go.

If keep also update the version of Hugo in mise.toml, it's easier to locally validate that we're happy with the new version.

This MR also would bring our build pipeline close to the version of Go specified in: https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/2200a2dd85cf145958d8c0eb73ca25245717c0aa/.gitlab-ci.yml#L22.

Pipeline validation How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Configure a local GitLab Docs environment.

  2. Check out this branch.

  3. Build the updated Docker image:

    docker buildx build --file dockerfiles/docs-gitlab-com-builder.Dockerfile --build-arg HUGO_VERSION_NEXT="0.148.2" .
  4. Run the updated Docker image:

    docker run --rm -ti c1323cdc8de091d719a84a9ef11d50ddf6d772f88646d1cd3be2d5e4bf6d30c4 sh
  5. Within the running container, verify an updated version of Go (go version) and Hugo (hugo version).

  6. Test a local build of the site:

Merge request acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited Aug 18, 2025 by Evan Read

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4