Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ci(deps): update dependency hugo to v0.109.0 - autoclosed #10

Closed
wants to merge 1 commit into from
Closed

ci(deps): update dependency hugo to v0.109.0 - autoclosed #10

wants to merge 1 commit into from

Conversation

renovate-tests
Copy link

This PR contains the following updates:

Package Update Change
hugo minor 0.73.0 -> 0.109.0

Release Notes

gohugoio/hugo (hugo)

v0.109.0

Compare Source

Hugo v0.109.0 is the last release of 2022 – and with that we're wishing all of you a very merry Christmas and a prosperous new year[^1].

Notable new features

Pass variables to SCSS/SASS

Hugo has had great SCSS/SASS support, but passing variables (e.g. theme colours from config) down to the transpiler has been much harder than it should.

In Hugo v0.109.0 we added a new vars option and you can finally just do:

{{ $vars := dict "color1" "blue" "color2" "green" "font_size" "24px" }}
{{ $opts := (dict "transpiler" "dartsass" "outputStyle" "compressed" "vars" $vars ) }}
{{ $r := resources.Get "scss/main.scss" | toCSS $opts }}

And then in the SCSS file:

@​use "hugo:vars" as v;

p {
    color: v.$color1;
    font-size: v.$font-size;
}

More examples here.

Hugo Module Workspaces

Workspace support was added in Go 1.18, and in this release Hugo finally gets solid support for it.

A common use case for a workspace is to simplify local development of a site with its theme modules.

A workspace can be configured in a *.work file and activated with the module.workspace setting, which for this use is commonly controlled via the HUGO_MODULE_WORKSPACE OS environment variable.

See the hugo.work file in the Hugo Docs repo for an example:

go 1.19

use .
use ../gohugoioTheme

Using the use directive, list all the modules you want to work on, pointing to its relative location. As in the example above, it's recommended to always include the main project (the ".") in the list.

With that you can start the Hugo server with that workspace enabled:

HUGO_MODULE_WORKSPACE=hugo.work hugo server --ignoreVendorPaths "**"

The --ignoreVendorPaths flag is added above to ignore any of the vendored dependencies inside _vendor. If you don't use vendoring, you don't need that flag. But now the server is set up watching the files and directories in the workspace and you can see your local edits reloaded.

Breadcrumbs

We have added a new .Ancestors method on Page that walks up the tree to the home page. With this, breadcrumbs templates can be greatly simplified:

<ol>
  <ul>
    {{- range .Ancestors.Reverse }}
      <li><a href="{{ .Permalink }}">{{ .Title }}</a></li>
    {{- end }}
    <li class="active" aria-current="page">
      <a href="{{ .Permalink }}">{{ .Title }}</a>
    </li>
  </ul>
</ol>
The path to /public now available in PostCSS

So you can do process.env.HUGO_PUBLISHDIR in your postcss.config.js to figure out where Hugo publishes
its files.

Note that the value will always be an absolute file path and will point to a directory on disk even when running hugo server in memory mode.

If you write to this folder from PostCSS when running the server, you could run the server with one of these flags:

hugo server --renderToDisk
hugo server --renderStaticToDisk

Note

Bug fixes

  • If you use the legacy libsass transpiler in toCSS and uses the cached build to avoid having the extended version installed on the CI server, you need to rebuild those assets and commit them to source control (e.g. with hugo --gc).
  • tpl/resources: Fix data race in ToCSS aa2c724 @​bep #​10542
  • tocss: Fix unquote case with double quotes 5d5f0a2 @​septs #​10555
  • resources/js: Fix some import discrepancies between Hugo and ESBuild b54de1b @​bep #​10527
  • parser/metadecoders: Fix spelling e0e63f3 @​lacamera

Improvements

Dependency Updates

Documentation

Build Setup

[^1]: We're working on some bigger and even more exiting Hugo features that will be ready early next year. Stay tuned!

v0.108.0

Compare Source

With Hugo v0.108.0 you can render standalone Markdown images without a surrounding paragraph. Both the HTML- and CommonMark-specification defines image as an inline element. For Markdown, this has meant that if you put an image on its own (not inlined in another paragraph), it would be wrapped in <p></p> tags, even if you provide your own Render Hook Template.

Now you can get by this annoyance by setting markup.goldmark.parser.wrapStandAloneImageWithinParagraph = false

[markup]
  [markup.goldmark]
    [markup.goldmark.parser]
      wrapStandAloneImageWithinParagraph = false
      [markup.goldmark.parser.attribute]
        block = true

In the above we have also enabled attribute support for Markdown blocks to illustrate another nice side effect of this; it's now possible to use Markdown attributes (e.g. CSS classes) on standalone images:

This is an inline image: ![Inline Image](/inline.jpg). Some more text.

![Block Image](/block.jpg)
{.blue}

The images in the above Markdown example would, given the hook template below, be rendered wrapped in a figure element with the blue CSS class applied in the latter example.

{{ if .IsBlock }}<figure class="{{ .Attributes.class }}"><img src="{{ .Destination | safeURL }}" alt="{{ .Text }}" /></figure>
{{ else }}<img src="{{ .Destination | safeURL }}" alt="{{ .Text }}" />{{ end }}

Two new fields are added to the render context passed to image render hooks:

Bug fixes

Improvements

Dependency Updates

Documentation

v0.107.0

Compare Source

This release is mostly interesting if you do code highlighting. We fixed a bottle neck which should show a significant performance boost for sites using code highlighting. Hugo's gohugo.io docs site builds ~20% faster. Also, Chroma, the highlighting library, is upgraded to v2.4.0 with new lexers and lots of improvements.

Bug fixes

Improvements

Dependency Updates

v0.106.0

Compare Source

Bug fixes

Dependency Updates

Documentation

v0.105.0

Compare Source

Bug fixes

Improvements

Dependency Updates

Documentation

Build Setup

v0.104.3

Compare Source

What's Changed

Note that none of the fixes below are regressions from v0.104.*; the first one, the GIF fix, comes from v0.101, back when we added support for processing animated GIFs.

v0.104.2

Compare Source

Fix htimes /: operation not permitted error on config changes when running the server. This regression was introduced in Hugo v0.104.1 4611b69 @​bep

v0.104.1

Compare Source

What's Changed

v0.104.0

Compare Source

Some bug fixes, dependency upgrades and a new $image.Colors method. This method returns a slice of the most dominant colors in an image. The library we use is implemented by @​marekm4 and is both fast and accurate. One use case for this may be to use as a placeholder before the image is loaded, as seen on this Hugo gallery [theme source]. You need a slow enough internet connection to notice this effect so you may want to try this with Chrome's dev console open and throttle the network to slow 3G, which would make it look something like this:

colorsani1.mp4

Bug fixes

Improvements

Dependency Updates

Documentation

v0.103.1

Compare Source

What's Changed

v0.103.0

Compare Source

There are 3 main topics in this release:

  • The hugo server finally comes with proper 404 support.
  • You can now use PostProcess'ed resources in all file types (e.g. JSON), not just HTML.
  • We have standardised the archive names for the release archives (as you can see further below). Hugo has since the first version used a rather odd and non-standard mixed case naming of the archive files (e.g. hugo_0.102.3_OpenBSD-64bit.tar.gz). We now use the standard GOOS/GOARCH values as-is, which makes it easier for people to script against. To avoid breakage when running on Netlify and similar, we create aliases for the most commonly downloaded Linux-archives on the old format and will continue to do so in the foreseeable future.

Bug fixes

Improvements

Dependency Updates

Build Setup

v0.102.3

Compare Source

What's Changed

v0.102.2

Compare Source

What's Changed

v0.102.1

Compare Source

What's Changed

v0.102.0

Compare Source

Note: there were an issue with the Deb Linux binaries (see #​10220), so those are now removed; will create a patch release with a fresh set later today.

This release adds Linux ARM64 extended archives (see issue #​8257). If you look behind the scenes of this, you may say that "this looks like a lot of work for one file", but the current serial build setup was already closing in on the timeout limits of CircleCI (mostly because of the relatively resource-intensive extended build with CGO/webp/libsass). So, we eventually had to do something. This release is built using Hugoreleaser, a custom build tool that allows us to partition the build step. The Linux ARM64 binaries are built in its own Docker container, and we also get a general speedup of the entire build:

image

In Circle CI, this is how the release flow looks like:

image

In the above, build_container1 is doing most of the work and is configured with parallelism: 7 and partitioned using $CIRCLE_NODE_TOTAL and $CIRCLE_NODE_INDEX:

image

See the CircleCI Config for details.

Notes

  • The MacOS archives have been replaced with universal/fat binaries that works on all MacOS platforms, named *macOS-universal.tar.gz.
  • These archives are removed: 32 bit Linux archives, Windows 32-bit and ARM, Linux ARM Deb. We may re-add some of these if enough people shout.

Bug fixes

Improvements

Dependency Updates

Build Setup

Documentation

v0.101.0

Compare Source

Hugo v0.101.0 comes with GIF animation image processing, a new hl_inline option for code highlighting, a new :slugorfilename permalink keyword, we now respect the NO_COLOR OS env var, and more.

This release represents 35 contributions by 9 contributors to the main Hugo code base.@​bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @​dependabot[bot], @​jmooring, and @​vanbroup for their ongoing contributions. Also a shoutout to @​CIAvash for his work on the Chroma highlighter.

Many have also been busy writing and fixing the documentation in hugoDocs,
which has received 3 contributions by 2 contributors.

Hugo now has:

Changes

v0.100.2

Compare Source

This release is mostly motivated by the fix for the panic experienced by people having blackfriday configured as defaultMarkdownHandler (#​9968). The Blackfriday support was removed in Hugo v0.100.0 after being deprecated with a warning for a long time.

  • Fix raw TOML dates in where/eq 0566bbf [@​b

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@renovate-tests renovate-tests changed the title ci(deps): update dependency hugo to v0.109.0 ci(deps): update dependency hugo to v0.109.0 - autoclosed Feb 1, 2025
@renovate-tests renovate-tests deleted the renovate/hugo-0.109.x branch February 1, 2025 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@renovate-tests