Bump actions/actions-runner from 2.319.1 to 2.320.0 in /images/meat-runner-22.04

[dependabot]

Bumps actions/actions-runner from 2.319.1 to 2.320.0.

Release notes

Sourced from actions/actions-runner's releases.

v2.320.0

What's Changed

• Adding Snapshot additional mapping tokens actions/runner#3468
• Create launch httpclient using the right handler and setting actions/runner#3476
• Fix missing default user-agent for jitconfig runner actions/runner#3473
• Cleanup back-compat code for interpreting Run Service status codes actions/runner#3456
• Add runner or worker to the useragent actions/runner#3457
• Handle Error Body in Responses from Broker actions/runner#3454
• Fix issues for composite actions (Run Service flow) actions/runner#3446
• Trace GitHub RequestId to log actions/runner#3442
• Add jq, git, unzip and curl to default packages installed actions/runner#3056
• Add pid to user-agent and session owner actions/runner#3432

Full Changelog: actions/runner@v2.319.1...v2.320.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.320.0/actions-runner-win-x64-2.320.0.zip -OutFile actions-runner-win-x64-2.320.0.zip
# Extract the installer
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$PWD\actions-runner-win-x64-2.320.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.320.0/actions-runner-win-arm64-2.320.0.zip -OutFile actions-runner-win-arm64-2.320.0.zip
# Extract the installer
</tr></table> 

... (truncated)

Changelog

Sourced from actions/actions-runner's changelog.

What's Changed

• Adding Snapshot additional mapping tokens actions/runner#3468
• Create launch httpclient using the right handler and setting actions/runner#3476
• Fix missing default user-agent for jitconfig runner actions/runner#3473
• Cleanup back-compat code for interpreting Run Service status codes actions/runner#3456
• Add runner or worker to the useragent actions/runner#3457
• Handle Error Body in Responses from Broker actions/runner#3454
• Fix issues for composite actions (Run Service flow) actions/runner#3446
• Trace GitHub RequestId to log actions/runner#3442
• Add jq, git, unzip and curl to default packages installed actions/runner#3056
• Add pid to user-agent and session owner actions/runner#3432

Full Changelog: actions/runner@v2.319.1...v2.320.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 ;
</tr></table> 

... (truncated)

Commits

• 78f2167 Fix release workflow to use distinct artifact names
• 4bf0e1b v2.320.0 release
• 149123c Prepare v2.320.0 (#3484)
• e292ec2 Adding Snapshot additional mapping tokens (#3468)
• 3696b7d Create launch httpclient using the right handler and setting. (#3476)
• 6d7446a fix missing default user-agent for jitconfig runner. (#3473)
• ddf41af Cleanup back-compat code for interpreting Run Service status codes (#3456)
• 0b0cb55 Add runner or worker to the useragent. (#3457)
• 4c0a43f Handle Error Body in Responses from Broker (#3454)
• 65764d9 Capature actions_type after resolving alpine container. (#3455)
• Additional commits viewable 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)