Hugo 0.93.0 Released

11 Likes

Hugo 0.93.0 packages

Brew - Hugo Brew package for macOS and Linux - updated :white_check_mark:
Snap Package - Hugo Snap (Snapcraft) package for Linux

  • traditional release - updated :white_check_mark:
  • extended release - updated :white_check_mark:

Docker/CI Image - Hugo Docker image for Continuous Integration - updated :white_check_mark:
Docker Image - klakegg/hugo - Other Hugo Docker image - updated :white_check_mark:
Debian (sid) - not yet updated :x: (Track link)
Ubuntu (hirsute) - not yet updated :x: (Track link )
Fedora Copr - Hugo RPM package for Fedora and CentOS - not yet updated :x:
Chocolatey Package - Hugo Chocolatey package for Windows

3 Likes

This version has 107 changes.

I haven’t finished reading or comprehending the prior release notes. There are no tutorials for Hugo releases like there are for Tailwind CSS. Why don’t we have a discussion about what one can do with this new release, such as what is now possible in comparison to the previous release?

And kudos for putting in so much effort.

Thanks

1 Like

@pitifi9191 this is a technical thread about the new release (where to get it…). If you’re curious about what the release is about, start a new thread, but the summary in the release notes should cover the big topic (even if it took us 107 commits to get there :-).

Also, Tailwind Labs is a multimillion dollar (guessing a little) company with several full time employees. Expecting an interactive release tutorial from a minor Hugo release is … not realistic.

5 Likes

brew - updated :white_check_mark:

1 Like

Also, the correct number is 68. And lot of them are very small.

git log v0.92.2..v0.93.0 --pretty=oneline | wc -l                    master ⬆ ✭
      68
1 Like

got it, thanks

please consider this at some point if you got free time.

I meant the changes shown here

yes, but I have no way of knowing what is important. for example the nextjs release follow a structure like this:

where Hugo have a h2 “Changes” with 107 changes mentioned under it without any categories so I have to check one by one. this is what I do as beginner don’t know if there is a better way.

thanks

0.93.0 ext. gives me some errors, both in hugo server and hugo making it unworkable. 0.92.2 ext works fine. All on Windows 10 + VS Code.

My stack: GitHub - 4044ever/Hugo-Tailwind-3.0: A barebone Hugo starter with Tailwind 3.0. Build your own theme on top.

Scripts:

"scripts": {
    "start": "concurrently npm:watch:*",
    "watch:tw": "tailwindcss -i ./assets/css/main.css -o ./assets/css/style.css --watch",
    "watch:hugo": "hugo server",
    "build": "hugo --minify" }
Start error:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli ‘G:\web\nodejs\node.exe’,
1 verbose cli ‘G:\web\nodejs\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘run’,
1 verbose cli ‘watch:hugo’
1 verbose cli ]
2 info using npm@6.14.15
3 info using node@v14.18.0
4 verbose run-script [ ‘prewatch:hugo’, ‘watch:hugo’, ‘postwatch:hugo’ ]
5 info lifecycle pizza@1.0.0~prewatch:hugo: pizza@1.0.0
6 info lifecycle pizza@1.0.0~watch:hugo: pizza@1.0.0
7 verbose lifecycle pizza@1.0.0~watch:hugo: unsafe-perm in lifecycle true
8 verbose lifecycle pizza@1.0.0~watch:hugo: PATH: G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;G:\web\hugo\pizza\node_modules.bin;G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;G:\web\hugo\pizza\node_modules.bin;C:\Python310\Scripts;C:\Python310;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\PuTTY;C:\Program Files\Git\cmd;G:\web\nodejs;C:\ProgramData\chocolatey\bin;C:\Users\user007\AppData\Local\Microsoft\WindowsApps;C:\WinNMP\bin;G:\web\Hugo\bin;;C:\Users\user007\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\user007\AppData\Roaming\npm
9 verbose lifecycle pizza@1.0.0~watch:hugo: CWD: G:\web\hugo\pizza
10 silly lifecycle pizza@1.0.0~watch:hugo: Args: [ ‘/d /s /c’, ‘hugo server’ ]
11 silly lifecycle pizza@1.0.0~watch:hugo: Returned: code: 2 signal: null
12 info lifecycle pizza@1.0.0~watch:hugo: Failed to exec watch:hugo script
13 verbose stack Error: pizza@1.0.0 watch:hugo: hugo server
13 verbose stack Exit status 2
13 verbose stack at EventEmitter. (G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess. (G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1058:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid pizza@1.0.0
15 verbose cwd G:\web\hugo\pizza
16 verbose Windows_NT 10.0.19043
17 verbose argv “G:\web\nodejs\node.exe” “G:\web\nodejs\node_modules\npm\bin\npm-cli.js” “run” “watch:hugo”
18 verbose node v14.18.0
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 2
22 error pizza@1.0.0 watch:hugo: hugo server
22 error Exit status 2
23 error Failed at the pizza@1.0.0 watch:hugo script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

Build error

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli ‘G:\web\nodejs\node.exe’,
1 verbose cli ‘G:\web\nodejs\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘run’,
1 verbose cli ‘build’
1 verbose cli ]
2 info using npm@6.14.15
3 info using node@v14.18.0
4 verbose run-script [ ‘prebuild’, ‘build’, ‘postbuild’ ]
5 info lifecycle pizza@1.0.0~prebuild: pizza@1.0.0
6 info lifecycle pizza@1.0.0~build: pizza@1.0.0
7 verbose lifecycle pizza@1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle pizza@1.0.0~build: PATH: G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;G:\web\hugo\pizza\node_modules.bin;C:\Python310\Scripts;C:\Python310;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\PuTTY;C:\Program Files\Git\cmd;G:\web\nodejs;C:\ProgramData\chocolatey\bin;C:\Users\user007\AppData\Local\Microsoft\WindowsApps;C:\WinNMP\bin;G:\web\Hugo\bin;;C:\Users\user007\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\user007\AppData\Roaming\npm
9 verbose lifecycle pizza@1.0.0~build: CWD: G:\web\hugo\pizza
10 silly lifecycle pizza@1.0.0~build: Args: [ ‘/d /s /c’, ‘hugo --minify’ ]
11 silly lifecycle pizza@1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle pizza@1.0.0~build: Failed to exec build script
13 verbose stack Error: pizza@1.0.0 build: hugo --minify
13 verbose stack Exit status 2
13 verbose stack at EventEmitter. (G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess. (G:\web\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1058:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid pizza@1.0.0
15 verbose cwd G:\web\hugo\pizza
16 verbose Windows_NT 10.0.19043
17 verbose argv “G:\web\nodejs\node.exe” “G:\web\nodejs\node_modules\npm\bin\npm-cli.js” “run” “build”
18 verbose node v14.18.0
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 2
22 error pizza@1.0.0 build: hugo --minify
22 error Exit status 2
23 error Failed at the pizza@1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

Note: A hugo will create this css link:
<link rel="stylesheet" href="__h_pp_l1_1_RelPermalink__e=" integrity="__h_pp_l1_1_Data.Integrity__e="/>

The direct hugo server output seems to be too long for this forum. Can find other way if required.

I am back with 0.92.2 , which works perfectly fine with my funny TailwindCSS 3.0 setup.

Hints are welcome!

PS: 0.93.1 gives me same erros.

Please open a new thread. this is not the place here.

And your error messages are anything but a hugo error. You should look at what you call your stack, but this are not error messages from hugo.

Continued here: 0.93.* giving "stack exceeds" error

Updated at test to rebuild the site. everything seems working as expected. Thank you.