CI: bump actions/checkout to v5 to remove Node 20 deprecation warning

[Copilot]

This updates the nginx 1.30 test workflow to stop using a GitHub Action version that runs on deprecated Node.js 20. The CI behavior is preserved; only the action runtime dependency is upgraded.

• Workflow dependency update

  • Updated .github/workflows/test-nginx-1.30.yml:
    • actions/checkout@v4 → actions/checkout@v5
  • Kept all job steps, matrix entries, and triggers unchanged.

• Scope

  • Applied the minimal safe change set focused on the reported warning in the existing workflow.

- name: Check out repository
- uses: actions/checkout@v4
+ uses: actions/checkout@v5

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cpanmetadb.plackperl.org
  • Triggering command: /usr/bin/wget /usr/bin/wget REDACTED --user-agent cpanminus/1.7047 perl/5.038002 --retry-connrefused -q -O - (dns block)
  • Triggering command: /usr/bin/wget /usr/bin/wget REDACTED --user-agent cpanminus/1.7047 perl/5.038002 --retry-connrefused -q -O - ame (dns block)
• dl.google.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)
• fastapi.metacpan.org
  • Triggering command: /usr/bin/wget /usr/bin/wget REDACTED --user-agent cpanminus/1.7047 perl/5.038002 --retry-connrefused -q -O - r (dns block)
  • Triggering command: /usr/bin/wget /usr/bin/wget REDACTED --user-agent cpanminus/1.7047 perl/5.038002 --retry-connrefused -q -O - ame (dns block)
• http://www.cpan.org:80/modules/02packages.details.txt.gz
  • Triggering command: /usr/bin/wget /usr/bin/wget REDACTED --user-agent cpanminus/1.7047 perl/5.038002 --retry-connrefused -q -O /root/.cpanm/sources/http%www.cpan.org/02packages.details.txt.gz (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Create a pull request in Securepoint/nginx-ntlm-modulev2 to update GitHub Actions workflow dependencies so the repository no longer emits the warning:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4

Context:

• Repository: Securepoint/nginx-ntlm-modulev2
• There is an existing workflow at .github/workflows/test-nginx-1.30.yml.
• A recent workflow run reported that actions/checkout@v4 is running on deprecated Node.js 20.
• The user wants a PR that resolves this warning.

Required work:

• Inspect the repository workflows, especially .github/workflows/test-nginx-1.30.yml, for usages of actions/checkout@v4 and any other actions that may trigger the same deprecated Node.js 20 runtime warning.
• Update affected action versions to supported versions that no longer rely on deprecated Node.js 20, while preserving existing workflow behavior.
• Keep the workflow YAML valid and stylistically consistent with the repo.
• Prefer the minimal safe change set needed to eliminate the warning.
• If any action upgrade has behavior differences or migration considerations, mention them clearly in the PR description.

Acceptance criteria:

• A PR is opened against the repository with the workflow updates.
• The deprecated Node.js 20 action warning for actions/checkout@v4 is addressed.
• Existing CI intent and behavior remain unchanged except for the dependency/runtime upgrade needed to remove the warning.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: does this work on "v0.9" tag?

Assistant: Yes — v0.9 would match this PR’s workflow trigger.

Why:

• The workflow adds these tag patterns:
  • v*
  • [0-9]*

v0.9 matches v*, so a push of tag v0.9 will trigger the workflow.

Relevant change:

on:
  push:
    branches:
      - main
    tags:
      - v*
      - '[0-9]*'
  pull_request:

A couple of notes:

• This is based on push events for tags, not GitHub Releases specifically.
• It should fire when the tag is created and pushed to the remote, e.g. git push origin v0.9.

If you want, I can also check whether the pattern is too broad and suggest a stricter match like v[0-9]+.[0-9]+* or similar.

User: ok. push the change. and when finished, create a tag for v0.9 release

Assistant: I can help with the PR, but I can’t do the final release/tagging step from here with the tools available.

What I can do:

• mark this PR ready / help verify it
• merge it if you want and if repository permissions/tooling allow it
• prepare the exact git commands for creating v0.9

What I can’t do directly here:

• create/push a Git tag, because there isn’t a tag/merge write tool available for that action in this session

To proceed safely, tell me one of these:

1. “merge PR 9” — and I’ll see if I can complete that via available GitHub operations
2. or “just give me the commands” — and I’ll give you the exact commands to merge and tag v0.9

Likely commands after merge would be:

git checkout main
git pull origin main
git tag v0.9
git push origin v0.9

If you want, I can also give you the GitHub CLI version.

User: update the node runner

Assistant: Do you want me to update the GitHub Actions runner version used by the workflow in Securepoint/nginx-ntlm-modulev2 by opening a new PR?

If yes, say:

• the target repo is Securepoint/nginx-ntlm-modulev2
• optionally which runner you want, e.g. ubuntu-24.04 or ubuntu-latest

If you want, I can also first inspect that workflow run and tell you exactly which runner version it’s currently using and what should be changed.

User: the node runner to avoid the warning "Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4,"

Assistant: You don’t fix that warning by changing runs-on to another Ubuntu image. The warning is about the JavaScript runtime used by the action itself, not the VM runner image.

For actions/checkout, the fix is to upgrade the action version. GitHub’s current docs show actions/checkout@v6 in examples, which indicates newer major versions are intended for current runtimes, while your warning specifically calls out actions/checkout@v4 running on deprecated Node.js 20. See Building and testing Node.js.

So the change you want is likely:

- uses: actions/checkout@v4
+ uses: actions/checkout@v6

If the workflow also uses other official actions pinned to older majors, they may need similar bumps.

If you want, I can open a PR in Securepoint/nginx-ntlm-modulev2 to update the workflow a...

This pull request was created from Copilot chat.