chore(deps): bump runs-on/action from 2.3.1 to 2.5.0

[dependabot]

Bumps runs-on/action from 2.3.1 to 2.5.0.

Release notes

Sourced from runs-on/action's releases.

v2.5.0

What's Changed

New

• Disk metrics report free and total bytes (disk_free, disk_total), and the post-step summary charts them.
• Disk metrics identify each mount's EBS volume with a new VolumeId dimension, so a sticky disk or snapshot volume on /var/lib/docker reports its own volume instead of the root volume's. (#68, closes #19)

Changed

• On RunsOn v3.4.0 and later, the runner agent reports the job cost in the "Complete runner" step, and show_costs only chooses how it is shown (inline, summary or off). On those stacks the action no longer calls the RunsOn cost API or DescribeAvailabilityZones. Older stacks keep the post-step cost report. (#70)
• Disk metrics now carry device and VolumeId dimensions. CloudWatch matches exact dimension sets, so dashboards or alarms that select disk metrics by their dimensions need the new ones.

v2.4.0

What's Changed

New

• sticky_cache: tool-cache persists RUNNER_TOOL_CACHE on the sticky disk, so toolchains downloaded by setup-* actions are reused by later jobs in the same sticky lineage. Linux and Windows. Run it before the setup-* actions. The mode hides the runner image's preinstalled toolchains for the job; read the README section before enabling it. (#54, #55)

Changed

• sccache: s3 scopes its S3 key prefix per repository and platform: cache/sccache/<repository-id>/<os>-<arch>/v1 instead of the shared cache/sccache. The first run after upgrading starts a cold cache for each repository and platform. Objects under the old prefix expire through the stack's cache lifecycle rule. Thanks @​garysassano (#58)
• Cost reporting is skipped when pricing is unavailable: the action logs an informational message instead of a warning, and prints no cost table or job summary. (#61)

Fixed

• sticky_cache: git: sparse and filter: blob:none checkouts of large repositories no longer fail with HTTP 400 / expected 'packfile' when git fetches the missing blobs. Checking the requested objects against the mirror is also much faster (one pass instead of one git process per object). Thanks @​zackerydev (#64)

Full Changelog: runs-on/action@v2.3.1...v2.4.0

Commits

• 17b5909 dist: rebuild binaries for v2.5.0
• e8a299c Merge branch 'main' into v2
• 1f79b1a Bump README to v2.5.0
• 1720eab Let the RunsOn agent report job costs on v3.4.0+ stacks (#70)
• e41074e dist: rebuild binaries
• 854c754 Publish the EBS VolumeId of each disk metric mount
• 742ac2b feat(metrics): publish disk free and total bytes
• dfae4d9 dist: rebuild binaries for v2.4.0
• de0c266 Merge branch 'main' into v2
• 040eadd Bump README to v2.4.0
• 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 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)