Bump actions/actions-runner from 2.316.1 to 2.317.0 in /images/meat-runner-22.04

[dependabot]

Bumps actions/actions-runner from 2.316.1 to 2.317.0.

Release notes

Sourced from actions/actions-runner's releases.

v2.317.0

What's Changed

• Do not give up when uploading steps metadata by @​yacaovsnc in actions/runner#3280
• Upgrade node20 to 20.13.1 by @​pje in actions/runner#3284
• Delete all the contentHash files by @​pje in actions/runner#3285
• Make it easy to install git on an Action Runner Image by @​jww3 in actions/runner#3273
• Install gpg-agent during actions/runner container image build by @​jww3 in actions/runner#3294

Full Changelog: actions/runner@v2.316.1...v2.317.0

Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet. To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository. See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners

Windows x64

We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.

The following snipped needs to be run on powershell:

# Create a folder under the drive root
mkdir \actions-runner ; cd \actions-runner
# Download the latest runner package
Invoke-WebRequest -Uri https://github.com/actions/runner/releases/download/v2.317.0/actions-runner-win-x64-2.317.0.zip -OutFile actions-runner-win-x64-2.317.0.zip
# Extract the installer
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$PWD\actions-runner-win-x64-2.317.0.zip", "$PWD")

[Pre-release] Windows arm64

Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.

We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.

The following snipped needs to be run on powershell:

# Create a folder under the drive root
mkdir \actions-runner ; cd \actions-runner
# Download the latest runner package
Invoke-WebRequest -Uri https://github.com/actions/runner/releases/download/v2.317.0/actions-runner-win-arm64-2.317.0.zip -OutFile actions-runner-win-arm64-2.317.0.zip
# Extract the installer
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$PWD\actions-runner-win-arm64-2.317.0.zip", "$PWD")

OSX x64

... (truncated)

Changelog

Sourced from actions/actions-runner's changelog.

What's Changed

• Do not give up when uploading steps metadata by @​yacaovsnc in actions/runner#3280
• Upgrade node20 to 20.13.1 by @​pje in actions/runner#3284
• Delete all the contentHash files by @​pje in actions/runner#3285
• Make it easy to install git on an Action Runner Image by @​jww3 in actions/runner#3273
• Install gpg-agent during actions/runner container image build by @​jww3 in actions/runner#3294

Full Changelog: actions/runner@v2.316.1...v2.317.0

Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet. To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository. See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners

Windows x64

We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.

The following snipped needs to be run on powershell:

# Create a folder under the drive root
mkdir \actions-runner ; cd \actions-runner
# Download the latest runner package
Invoke-WebRequest -Uri https://github.com/actions/runner/releases/download/v<RUNNER_VERSION>/actions-runner-win-x64-<RUNNER_VERSION>.zip -OutFile actions-runner-win-x64-<RUNNER_VERSION>.zip
# Extract the installer
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$PWD\actions-runner-win-x64-<RUNNER_VERSION>.zip", "$PWD")

[Pre-release] Windows arm64

Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.

We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.

The following snipped needs to be run on powershell:

# Create a folder under the drive root
mkdir \actions-runner ; cd \actions-runner
# Download the latest runner package
Invoke-WebRequest -Uri https://github.com/actions/runner/releases/download/v<RUNNER_VERSION>/actions-runner-win-arm64-<RUNNER_VERSION>.zip -OutFile actions-runner-win-arm64-<RUNNER_VERSION>.zip
# Extract the installer
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$PWD\actions-runner-win-arm64-<RUNNER_VERSION>.zip", "$PWD")

OSX x64

... (truncated)

Commits

• 6dc005e Update releaseVersion
• 84b1bea Prepare relese 2.317.0 (#3311)
• ce4d7be Bump xunit from 2.4.1 to 2.7.1 in /src (#3242)
• bd7235e Install gpg-agent during actions/runner container image build (#3294)
• 0f15173 Make it easy to install git on an Action Runner Image (#3273)
• 76dc3a2 Upgrade node20: 20.8.1 → 20.13.1 (#3284)
• c67e7f2 Delete all the contentHash files (#3285)
• 54052b9 Also do not give up when uploading steps metadata (#3280)
• f2c05de Prep 2.316.1 Release (#3272)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)