[helio-frota]

Summary by Sourcery

Upgrade the project’s Node.js baseline from version 22 to version 24 across development, build, CI, and documentation workflows.

Enhancements:

• Update development, documentation, and CI environments to require Node.js 24.

Build:

• Use Node.js 24 when building binaries and setting up the console environment.

CI:

• Run documentation checks and builds with Node.js 24.

Documentation:

• Update source-build, UI, and end-to-end testing prerequisites to reference Node.js 24.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The pull request updates all identified Node.js runtime configuration points from version 22 to version 24, covering the reusable console setup action and documentation-related CI jobs while preserving existing setup and caching behavior.

File-Level Changes

Change	Details	Files
Upgrade CI and local console setup to use Node.js 24.	Change the shared console setup action from Node.js 22 to Node.js 24 while retaining npm dependency caching. Run documentation checks and builds on Node.js 24 in the CI and documentation workflows.	.github/actions/setup-console/action.yaml .github/workflows/ci.yaml .github/workflows/docs.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[helio-frota]

thanks @desmax74 🚀

[ctron]

Wouldn't we need some updated to the release workflow as well?

[helio-frota]

I found nothing when searching about node version on release.yaml 🤔 🤷‍♂️

[ctron]

As it's failing in the vendoring step: https://github.com/guacsec/trustify/actions/runs/40687430872/job/122813832899

[helio-frota]

yeah thanks ... I think this will probably work.. I updated some missing READMEs...

pushd vendor/trustify-ui/res
npm ci --ignore-scripts
popd

this happens on build-binary.yaml which uses uses actions/checkout@v7 which defaults to node24

[[[ which is weird because this is not inheriting other gh-actions I changed 🤔 ]]]

[ctron]

Ok, then we'll merge and find out.

[helio-frota]

@ctron that is related to the ubuntu version apparently (instead of actions/checkout@v7) ... I got this from google search -- file updated 👍

On the standard GitHub Actions runner image for Ubuntu 24.04 (ubuntu-24.04 or ubuntu-latest), the default pre-installed version of Node.js on the system PATH is 22.23.3

[update] yeah : https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md#language-and-runtime

[ctron]

so, we need to update the node version in that job too?

[helio-frota]

so, we need to update the node version in that job too?

sounds weird to me as well but yes because this workflow is focused on rust - uses: ./.github/actions/setup-rust and then it grabs nodejs default from the ubuntu-24.04.

[trustify-ci-bot]

Backport failed for release/0.7.z, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/0.7.z
git worktree add -d .worktree/backport-2822-to-release/0.7.z origin/release/0.7.z
cd .worktree/backport-2822-to-release/0.7.z
git switch --create backport-2822-to-release/0.7.z
git cherry-pick -x 56b3611589d4d272af0587889a7605353d2e35b8