fix(ci): bump artifact actions to node24 runtimes

[lwiles692]

Description

GitHub Actions runners are deprecating Node.js 20: steps that still target node20 get force-run on Node 24 with a deprecation warning (see the changelog). Consumers of this action currently see:

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@ea165f8

This bumps every actions/upload-artifact / actions/download-artifact usage in the repo to the Node 24 runtimes:

File	Before	After
action.yml	upload-artifact@v4.6.2 (SHA-pinned, node20)	upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a (SHA-pinned, v7.0.1, node24)
.github/workflows/release.yml	upload-artifact@v4	upload-artifact@v7
.github/workflows/release.yml (×2)	download-artifact@v4	download-artifact@v7

Compatibility notes:

• All inputs in use (name, path, if-no-files-found; pattern, merge-multiple) exist unchanged in v7.
• upload-artifact v7 adds an archive input that defaults to true, so the existing multi-file zipped upload behavior is preserved.
• v6/v7 of both actions require Actions Runner ≥ 2.327.1. GitHub-hosted runners already satisfy this; only consumers on older self-hosted runners need to update their runner before picking this up.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring (no functional changes)
• Documentation update
• CI / Build / Tooling

How Has This Been Tested?

• make test passes locally
• Manual testing (describe below)

Verified against actions/upload-artifact and actions/download-artifact release notes / action.yml that the pinned v7.0.1 runs on node24 and that every input used here is present with the same semantics. Pure workflow/action version bumps — no source code touched.

Checklist

• My code follows the project's coding style (go fmt, go vet)
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly (if applicable)
• I have signed the CLA

Related Issues

None — preemptive cleanup driven by the runner-side Node 20 deprecation warning.

[CLAassistant]

All committers have signed the CLA.

[wu21-web]

I think there is no need for change really.

[lwiles692]

I think there is no need for change really.

When used in GitHub Actions, a warning is triggered that may confuse users. In fact, this dependency is brought in by the OCR package itself and is not part of the user’s repository. Avoid using outdated versions and upgrade to the officially recommended version.

[wu21-web]

I think there is no need for change really.

When used in GitHub Actions, a warning is triggered that may confuse users. In fact, this dependency is brought in by the OCR package itself and is not part of the user’s repository. Avoid using outdated versions and upgrade to the officially recommended version.

@lwiles692 This reply looks like it is generated by AI.

[wu21-web]

And also @lwiles692 , please check @Fanzzzd #856 and it's related itemd. I remember that it was kept as v4 intentionally.

[lwiles692]

I think there is no need for change really.

When used in GitHub Actions, a warning is triggered that may confuse users. In fact, this dependency is brought in by the OCR package itself and is not part of the user’s repository. Avoid using outdated versions and upgrade to the officially recommended version.

@lwiles692 This reply looks like it is generated by AI.

This is a real issue I encountered while using OCR in my own repository. At the time, I had some doubts, but after troubleshooting, the conclusion matched my description. Functionally, there is indeed no impact at the moment. If you don’t consider it a problem, feel free to close it.

[wu21-web]

You can safely ignore this warning, the issue it created is a minor.