WARNING: Cache entry deserialization failed, entry ignored

WARNING: Cache entry deserialization failed, entry ignored

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/checkout@v4, actions/download-artifact@v4.1.7, actions/setup-python@v2, actions/upload-artifact@v4, actions/upload-artifact@v4.4.0. 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/

The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 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 keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.

Release not found

The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 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 keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.

The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 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 keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.