Bumps the CI actions to their latest majors to clear the recurring "Node.js 20
is deprecated" warnings (the pinned actions bundled Node 20, which GitHub is
retiring on runners):
- actions/checkout v4 -> v7
- actions/setup-dotnet v4 -> v5
- actions/upload-artifact v4 -> v7
- actions/setup-node v4 -> v6
- actions/stale v9 -> v10
atomicjar/testcontainers-cloud-setup-action is already on the latest major (v1).
Only the action version tags change. All bumped majors run on Node.js 24 and
require Actions Runner >= v2.327.1, which the GitHub-hosted runners used here
always satisfy. checkout v7's fork-PR checkout block only applies to
pull_request_target/workflow_run (not used here), and setup-node's auto-cache
only triggers with a packageManager field in package.json (not present), so
behavior is unchanged. Validated with actionlint.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Currently the CIFS Tests on macos and windows require it to run in cloud mode, which means the port binding would not match default netbios/directtcp protocol standards as the container port allocation is random and the backend does not support specifying explicit ports.
The remaining tests on linux nevertheless already grants some degree of assurance the backend is working.
CIFS was removed from CI as port mapping issues were detected in the TestContainers setup (port bindings on testcontainers are not mapped 1:1 and have to be fetched at runtime). At the same time, CIFS backed does not support specifying a different port other than the standard 139 and 445 determined by transport option, either NetBiosOverTCP or DirectTCPTransport).
By using a concurrency group called "duplicati-ci-livetests' the goal so to avoid having issues with multiple PRs triggering the live tests in parallel which causes false-fails on tests because they share credentials for cloud provided backends and running in parallel during tests causes file conflicts.
