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	v5	v6	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.

[CLAassistant]

All committers have signed the CLA.

[zachcoleman]

will try when GH isn't having issues

[coveralls]

Pull Request Test Coverage Report for Build 21788744369

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 20179835394:	0.0%
Covered Lines:	786
Relevant Lines:	786

---

💛 - Coveralls

[justinhwang]

I think the check is failing because this block already ran:

  finish:
    needs: test
    if: ${{ always() }}
    runs-on: ubuntu-latest
    steps:
      - uses: actions/setup-go@v6
        with:
          go-version: 1.25
      - name: install-goveralls
        run: go install github.com/mattn/goveralls@latest
      - name: finish-coverage-parallel
        env:
          COVERALLS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: goveralls -parallel-finish -service=github

But unsure how to trigger a wholesale rerun so we stop getting the build errs - either way we can test with a followup PR (maybe bumping to go 1.26) so I'm fine with ignoring the errs