Update build.yml

[Dargon789]

Please, go through these steps before you request a review:

📝 Describe your changes

🔎 Attach a source of truth or evidence that allows reviewers to confirm the changes independently

Summary by Sourcery

Build:

• Bump actions/setup-node from v3 to v5 in the build workflow to keep the Node setup action up to date.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the GitHub Actions workflow to use the latest major version of the Node setup action while keeping the existing Node configuration and caching behavior unchanged.

File-Level Changes

Change	Details	Files
Upgrade the GitHub Actions Node setup action to the latest major version in the build workflow.	Bump actions/setup-node from v3 to v5 in the build job Retain existing Node LTS version selection via 'lts/*' Preserve npm caching configuration for dependency installation	.github/workflows/build.yml

---

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 found 1 issue, and left some high level feedback:

• When bumping actions/setup-node to v5, verify that all other actions in this workflow are compatible with the Node 20 runner environment that v5 uses by default.
• Consider pinning actions/setup-node@v5 to a specific commit SHA in addition to the major tag to reduce the risk of supply-chain or unexpected behavior changes in future v5 releases.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- When bumping `actions/setup-node` to v5, verify that all other actions in this workflow are compatible with the Node 20 runner environment that v5 uses by default.
- Consider pinning `actions/setup-node@v5` to a specific commit SHA in addition to the major tag to reduce the risk of supply-chain or unexpected behavior changes in future v5 releases.

## Individual Comments

### Comment 1
<location> `.github/workflows/build.yml:18` </location>
<code_context>
       - run: corepack enable

-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v5
         with:
           node-version: 'lts/*'
</code_context>

<issue_to_address>
**🚨 suggestion (security):** Consider pinning `actions/setup-node` to a specific commit SHA for stronger supply-chain guarantees.

Using only the floating `v5` tag means the workflow will automatically pick up any future changes to `actions/setup-node`, including potentially breaking or compromised versions. To harden the workflow, reference a specific commit SHA instead (e.g., `actions/setup-node@<commit-sha>`), with an inline comment like `# v5` so it’s clear which major version you’re on. This keeps behavior stable and upgrades explicit and reviewable.

Suggested implementation:

```
      - run: corepack enable

      - uses: actions/setup-node@<commit-sha> # v5
        with:
          node-version: 'lts/*'
          cache: npm

```

Replace `<commit-sha>` with the actual commit SHA corresponding to the desired `v5` release of `actions/setup-node`. You can obtain this by:
1. Going to https://github.com/actions/setup-node/releases.
2. Choosing the `v5` release you want to pin to.
3. Copying its commit SHA and substituting it for `<commit-sha>` in the workflow.
</issue_to_address>

---

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

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}