Upgrade GitHub Actions for Node 24 compatibility

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action	Old Version(s)	New Version	Release	Files
actions/checkout	v1	v6	Release	build.yml
actions/setup-java	v2	v5	Release	build.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

• Node 20 EOL: April 2026
• Node 24 default: March 4th, 2026
• Action: Update to latest action versions that support Node 24

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

[Craigacp]

Looks like something changed in the default checkout logic (probably in v2, which I realise was more than 5 years ago) and now master isn't available on the worker which we use to determine which files were changed so we only run the linter on them. Looking at the docs I think if we set fetch_depth to 0 it should do a full clone and things should be as they were.

[salmanmkc]

Looks like something changed in the default checkout logic (probably in v2, which I realise was more than 5 years ago) and now master isn't available on the worker which we use to determine which files were changed so we only run the linter on them. Looking at the docs I think if we set fetch_depth to 0 it should do a full clone and things should be as they were.

Yeah that seems about right, this should hopefully work now, if not we might need to do a git checkout of master.

[Craigacp]

Thanks!