proposal: update node to a more recent version

[retorquere]

Checklist

• I am using the latest version of this action.
• I have read the latest README and followed the instructions.
• I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal

update node to a more recent version. GHA is reporting that node 16 actions are deprecated

Describe the solution you'd like

An update to a newer node version

Describe alternatives you've considered

Manually installing hugo

Additional context

None

[tohn]

Got this warning as well:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: peaceiris/actions-hugo@v2.6.0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

I think #641 does exactly that? And #614 is obsolete now 😉

[retorquere]

I think #641 does exactly that?

Seems like it does.

[daviddavo]

But we still need a release so github action's picks it up automatically

[jesseadams]

@peaceiris Can we please get a new release?

[ricomariani]

UPDATE: peaceiris/actions-hugo@v3 is now available, do not use the workaround below.

Lacking a release and with the deadline looming I made a fork and published a release with the release.sh script:

I am now able to do this:

uses: ricomariani/actions-hugo@sha-deleted-for-your-safety-use-the-release-above

This works for me but it won't be maintained further. If you're stuck you can use it. I don't know if there are known bugs in 'main' on the maintained branch but if main is good enough for you there's a published release now.

[peaceiris]

#647 (comment)

[ricomariani]

peaceiris/actions-hugo@v3 is working for me. I removed the SHA in my comment above so nobody will use it by accident. I will likely delete my fork in a few weeks just in case someone is still using the workaround SHA.

[peaceiris]

Thank you so much @ricomariani!

[github-actions]

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

Log | Bot Usage