[claude]

Requested by Samuel Attard · Slack thread

The setup-node steps here ask for a floating Node version (lts/-1), which setup-node satisfies from the runner's tool cache before checking for anything newer, so CI can keep running an older patch after a Node security release. Setting check-latest makes it resolve the newest matching release and only download when the cached copy is stale.

---

Generated by Claude Code

[claude]

I reviewed this PR and didn't find any bugs. The repo's CODEOWNERS file covers every path, though, so a code owner still has to sign off on it.

What was reviewed:

• All four actions/setup-node steps (check-sdk-version.yml, lint.yml with two jobs, test.yml) now set check-latest: true next to node-version: lts/-1. No setup-node step was missed.
• The action SHA pins, the # tag: comments and the actions/cache steps are unchanged. The YAML indentation matches each file.

Extended reasoning...

The change adds one line, check-latest: true, to each of the four setup-node steps in three CI workflow files, four lines in total. It doesn't touch application code, secrets, permissions or action pins. The only behavior change is that CI resolves the newest lts/-1 release from the network instead of using the runner's cached version. The change is trivial, but I didn't approve because the root CODEOWNERS file assigns every path (*) to code owners.