dependabot[bot] opened a new pull request, #26076: URL: https://github.com/apache/datafusion/pull/26076
Bumps [runs-on/action](https://github.com/runs-on/action) from 2.3.1 to 2.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/runs-on/action/releases">runs-on/action's releases</a>.</em></p> <blockquote> <h2>v2.5.0</h2> <h2>What's Changed</h2> <h3>New</h3> <ul> <li><strong>Disk metrics report free and total bytes</strong> (<code>disk_free</code>, <code>disk_total</code>), and the post-step summary charts them.</li> <li><strong>Disk metrics identify each mount's EBS volume</strong> with a new <code>VolumeId</code> dimension, so a sticky disk or snapshot volume on <code>/var/lib/docker</code> reports its own volume instead of the root volume's. (<a href="https://redirect.github.com/runs-on/action/issues/68">#68</a>, closes <a href="https://redirect.github.com/runs-on/action/issues/19">#19</a>)</li> </ul> <h3>Changed</h3> <ul> <li><strong>On RunsOn v3.4.0 and later, the runner agent reports the job cost</strong> in the "Complete runner" step, and <code>show_costs</code> only chooses how it is shown (<code>inline</code>, <code>summary</code> or off). On those stacks the action no longer calls the RunsOn cost API or <code>DescribeAvailabilityZones</code>. Older stacks keep the post-step cost report. (<a href="https://redirect.github.com/runs-on/action/issues/70">#70</a>)</li> <li><strong>Disk metrics now carry <code>device</code> and <code>VolumeId</code> dimensions.</strong> CloudWatch matches exact dimension sets, so dashboards or alarms that select disk metrics by their dimensions need the new ones.</li> </ul> <h2>v2.4.0</h2> <h2>What's Changed</h2> <h3>New</h3> <ul> <li><strong><code>sticky_cache: tool-cache</code></strong> persists <code>RUNNER_TOOL_CACHE</code> on the sticky disk, so toolchains downloaded by <code>setup-*</code> actions are reused by later jobs in the same sticky lineage. Linux and Windows. Run it before the <code>setup-*</code> actions. The mode hides the runner image's preinstalled toolchains for the job; read the README section before enabling it. (<a href="https://redirect.github.com/runs-on/action/issues/54">#54</a>, <a href="https://redirect.github.com/runs-on/action/issues/55">#55</a>)</li> </ul> <h3>Changed</h3> <ul> <li><strong><code>sccache: s3</code> scopes its S3 key prefix per repository and platform</strong>: <code>cache/sccache/<repository-id>/<os>-<arch>/v1</code> instead of the shared <code>cache/sccache</code>. 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 <a href="https://github.com/garysassano"><code>@​garysassano</code></a> (<a href="https://redirect.github.com/runs-on/action/issues/58">#58</a>)</li> <li><strong>Cost reporting is skipped when pricing is unavailable</strong>: the action logs an informational message instead of a warning, and prints no cost table or job summary. (<a href="https://redirect.github.com/runs-on/action/issues/61">#61</a>)</li> </ul> <h3>Fixed</h3> <ul> <li><strong><code>sticky_cache: git</code></strong>: sparse and <code>filter: blob:none</code> checkouts of large repositories no longer fail with <code>HTTP 400</code> / <code>expected 'packfile'</code> when git fetches the missing blobs. Checking the requested objects against the mirror is also much faster (one pass instead of one <code>git</code> process per object). Thanks <a href="https://github.com/zackerydev"><code>@​zackerydev</code></a> (<a href="https://redirect.github.com/runs-on/action/issues/64">#64</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/runs-on/action/compare/v2.3.1...v2.4.0">https://github.com/runs-on/action/compare/v2.3.1...v2.4.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/runs-on/action/commit/17b59092eb37ebfdbb034460892887c09100eaa3"><code>17b5909</code></a> dist: rebuild binaries for v2.5.0</li> <li><a href="https://github.com/runs-on/action/commit/e8a299c27a9b6542f2b1abac77f678f05ecae456"><code>e8a299c</code></a> Merge branch 'main' into v2</li> <li><a href="https://github.com/runs-on/action/commit/1f79b1a3eb52ec9a8b9500bf7786cc1a3c114e8f"><code>1f79b1a</code></a> Bump README to v2.5.0</li> <li><a href="https://github.com/runs-on/action/commit/1720eab4acafbe92a134d8be4bfd51d6a69973c1"><code>1720eab</code></a> Let the RunsOn agent report job costs on v3.4.0+ stacks (<a href="https://redirect.github.com/runs-on/action/issues/70">#70</a>)</li> <li><a href="https://github.com/runs-on/action/commit/e41074efcb4c4b1bf558e289909f8107c289f7d1"><code>e41074e</code></a> dist: rebuild binaries</li> <li><a href="https://github.com/runs-on/action/commit/854c754abf4ac53ecae0a5f03937656288bb40c2"><code>854c754</code></a> Publish the EBS VolumeId of each disk metric mount</li> <li><a href="https://github.com/runs-on/action/commit/742ac2bd03e36ced34e7739d2bb2c8bf889e29db"><code>742ac2b</code></a> feat(metrics): publish disk free and total bytes</li> <li><a href="https://github.com/runs-on/action/commit/dfae4d98c5537a0dc7bbb7e6b9211f30ba240f6d"><code>dfae4d9</code></a> dist: rebuild binaries for v2.4.0</li> <li><a href="https://github.com/runs-on/action/commit/de0c2669deeb30a5528b49a95367d08d886d96c3"><code>de0c266</code></a> Merge branch 'main' into v2</li> <li><a href="https://github.com/runs-on/action/commit/040eadd90efbac8f9ef4b3813afd46d5d5202762"><code>040eadd</code></a> Bump README to v2.4.0</li> <li>Additional commits viewable in <a href="https://github.com/runs-on/action/compare/efac073ea2507ec18797de3a81704201ade11d9d...17b59092eb37ebfdbb034460892887c09100eaa3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
