Skip to content

Clippy

Clippy #7824

Triggered via merge group June 13, 2026 04:04
Status Failure
Total duration 12m 49s
Artifacts

clippy.yml

on: merge_group
Determine toolchains
7s
Determine toolchains
Matrix: cargo clippy
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 23 warnings, and 3 notices
cargo clippy (ubuntu-24.04, nightly)
Process completed with exit code 1.
cargo clippy (macos-15, nightly)
Process completed with exit code 1.
cargo clippy (windows-2025, nightly)
Process completed with exit code 1.
cargo clippy (macos-15, nightly)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
cargo clippy (macos-15, nightly)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, nightly)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (macos-15, nightly)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, nightly)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
cargo clippy (macos-15, nightly)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (macos-15, stable)
The following taps are not trusted: aws/tap azure/bicep Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
cargo clippy (macos-15, stable)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, stable)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (macos-15, stable)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, stable)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
cargo clippy (macos-15, stable)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (macos-15, 1.90.0)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
cargo clippy (macos-15, 1.90.0)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, 1.90.0)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (macos-15, 1.90.0)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
cargo clippy (macos-15, 1.90.0)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
cargo clippy (macos-15, 1.90.0)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
cargo clippy (windows-2025, nightly)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cargo clippy (windows-2025, nightly)
Cache save failed.
cargo clippy (windows-2025, 1.90.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cargo clippy (windows-2025, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cargo clippy (windows-2025, stable)
Cache save failed.
cargo clippy (windows-2025, nightly)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
cargo clippy (windows-2025, 1.90.0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
cargo clippy (windows-2025, stable)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026