Skip to content

Fix poetry installation in CI #2056

Fix poetry installation in CI

Fix poetry installation in CI #2056

Triggered via push June 16, 2026 20:55
Status Success
Total duration 30m 26s
Artifacts 43
Matrix: build-spidermonkey-unix
build-spidermonkey-win
19s
build-spidermonkey-win
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 142 warnings
build-and-test (macos-14, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
build-and-test (macos-14, 3.8)
WARNING: Cache entry deserialization failed, entry ignored
build-and-test (macos-14, 3.10)
WARNING: Cache entry deserialization failed, entry ignored
build-and-test (macos-14, 3.9)
WARNING: Cache entry deserialization failed, entry ignored
build-spidermonkey-unix (macos-14, 3.10)
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@v4, actions/upload-artifact@v4. 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/
build-spidermonkey-unix (macos-15-intel, 3.10)
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@v4, actions/upload-artifact@v4. 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/
build-spidermonkey-win
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@v4, actions/upload-artifact@v4. 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/
build-spidermonkey-unix (ubuntu-22.04, 3.10)
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@v4, actions/upload-artifact@v4. 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/
build-spidermonkey-unix (ubuntu-22.04-arm, 3.10)
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@v4, actions/upload-artifact@v4. 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/
sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.14)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.14)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.14)
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.
build-and-test (macos-14, 3.14)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.14)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.14)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.14)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.14)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (ubuntu-22.04-arm, 3.8)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.10)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (windows-2022, 3.9)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.13)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.8)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.12)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.11)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.12)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.14)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04-arm, 3.9)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.11)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.14)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.10)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.10)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.10)
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.
build-and-test (macos-15-intel, 3.10)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.10)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.10)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.10)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.10)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.9)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.9)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.9)
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.
build-and-test (macos-15-intel, 3.9)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.9)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.9)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.9)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.9)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (windows-2022, 3.10)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.10)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.9)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (windows-2022, 3.12)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (windows-2022, 3.14)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (windows-2022, 3.8)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (windows-2022, 3.13)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (ubuntu-22.04, 3.13)
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@v4, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.8)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.8)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.8)
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.
build-and-test (macos-14, 3.8)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.8)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.8)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.8)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.8)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.13)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.13)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.13)
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.
build-and-test (macos-15-intel, 3.13)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.13)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.13)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.13)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.13)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.11)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.11)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.11)
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.
build-and-test (macos-15-intel, 3.11)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.11)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.11)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.11)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.11)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (windows-2022, 3.11)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.13)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.13)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.13)
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.
build-and-test (macos-14, 3.13)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.13)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.13)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.13)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.13)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.8)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.8)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.8)
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.
build-and-test (macos-15-intel, 3.8)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.8)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.8)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.8)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.8)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.11)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.11)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.11)
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.
build-and-test (macos-14, 3.11)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.11)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.11)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.11)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.11)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.10)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.10)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.10)
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.
build-and-test (macos-14, 3.10)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.10)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.10)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.10)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.10)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.9)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.9)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.9)
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.
build-and-test (macos-14, 3.9)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.9)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.9)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.9)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.9)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.12)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-14, 3.12)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.12)
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.
build-and-test (macos-14, 3.12)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.12)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-14, 3.12)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-14, 3.12)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-14, 3.12)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.12)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.12)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.12)
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.
build-and-test (macos-15-intel, 3.12)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.12)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.12)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.12)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.12)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.14)
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@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
build-and-test (macos-15-intel, 3.14)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-15-intel, 3.14)
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.
build-and-test (macos-15-intel, 3.14)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.14)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
build-and-test (macos-15-intel, 3.14)
Skipping hashicorp/tap because it is not trusted. Run `brew trust hashicorp/tap` to trust it.
build-and-test (macos-15-intel, 3.14)
Skipping azure/bicep because it is not trusted. Run `brew trust azure/bicep` to trust it.
build-and-test (macos-15-intel, 3.14)
Skipping aws/tap because it is not trusted. Run `brew trust aws/tap` to trust it.
publish-nightly
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@v4, actions/download-artifact@v4, actions/upload-artifact@v4. 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/
publish-archive
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@v5. 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/

Artifacts

Produced during runtime
Name Size Digest
docs-27647581251-943face1daff34a97dab0c7f168fba380bc91597
2.81 MB
sha256:acbc00ecd380a4a6e727490080b77df79fb24d4cd99e30e5945020fac0d5e49f
github-pages Expired
584 MB
sha256:a199aa3b0001c5043f4151eebd972152a0f3ac93202246f553c3d6e46c3d3fe5
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Linux-ARM64
52.3 MB
sha256:93a09c60ddca7d622d89a1a4a14651cc4b8704e01d10557235fe59552c496d74
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Linux-X64
52.1 MB
sha256:02aba39180331ae15811953135320c582fa9f284849493db0ca2642c43f37e2a
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Windows-X64
30.3 MB
sha256:921473e2baa0c1f9356a1855f678db215d246aec13aeef852c7b426c77953e90
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-macOS-ARM64
45.8 MB
sha256:fb06b961831083a6f45397326c850133edb7e4ede5426b52854aed35567513f7
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-macOS-X64
46.1 MB
sha256:24e9a09aed638ede700ba0c5a970e4910387d1f693507cade4851afb0a5a9467
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.10
21 MB
sha256:cf09148a555d2da56b0ac7e297bd89d4317ee19dfc4545638dc5b3fe7fdf1e42
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.11
21 MB
sha256:1487df45626b942e9254e29f9e0491bb8782deecc47a1a0a388589cb31dc5e52
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.12
21.1 MB
sha256:67180860a04e6b59541bf7543d4f74d60e94fc973481dc4237c11cc119e0eb9f
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.13
21 MB
sha256:39bc487fbfb2d8738d042571e5b337258a38bf1cae121aa510e5b44fe980b647
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.14
21 MB
sha256:fb11bf9737736356385e5ee019851beb7c5eba9c7b3eb57ce3cebe28802b18eb
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.8
21 MB
sha256:83eea58795893666f5b4f57ca3d3d4685ad788cf3b7592ef973100b8668cdbd7
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_ARM64_Python3.9
21 MB
sha256:d1beee617de6c6470fa8a53ef0dfd8269ebbe9cf1f0130637de152c88caad2d9
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.10
21.2 MB
sha256:dabeceb313b449945a52f95f205deb12a9f924c62a850d932509216644c5cdab
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.11
21.2 MB
sha256:cd4419a2adf03eb5cc469327b803bf8c9f18f6295b2b4e69190a307abadd0aa5
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.12
21.3 MB
sha256:a84e068cb6e9532533ea318069e84b7c0079e7276875a2581f5352de0c3b6206
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.13
21.2 MB
sha256:d735824aed0892166e9f0ffe5553853b9b4c580f3375320015913caa2d153002
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.14
21.2 MB
sha256:38903a0d6797ce151c049d09c1f6fe5e47dbcf0948d78eed298a62c2dbf6636c
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.8
21.2 MB
sha256:d52547945acffd47ebaf4a81a654de96406dff27c22a9c61db5b889ff6e480d4
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Linux_X64_Python3.9
21.2 MB
sha256:d5281835c03dfc6156ea6db89af00ca068ea2d699e66acd6fb5e30fad57f30cb
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.10
12.4 MB
sha256:7b268d3df3c33042c96039c8beb056243549bb65a6f92d5500f00f1d96643e79
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.11
12.4 MB
sha256:75cf40fac7525371b65cafbfd01dbae65ee2c605e355c473f24f6c7d3ddcfc95
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.12
12.4 MB
sha256:7957e97b01d5c4f50bee425fdc404f88b78ed0d7f2ae30f772a4fb27b8c86333
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.13
12.4 MB
sha256:4c1281b62de8b5bfda4c2ea2db5bf307540b9d6b1349ec707afcea85378dcb43
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.14
12.7 MB
sha256:1c62835d09067f6579dc4b212adb22b3a453a95f63f59690a17f3f97f5d55415
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.8
12.4 MB
sha256:ae791b4d56611b4fecb004056e5ceaf64dc4fbbeebef435034a9ae78be867930
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-Windows_X64_Python3.9
12.4 MB
sha256:4c088d99b7c194af18ca24928711639ac37f33c632414dda304ffe1c24549eb5
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.10
14.1 MB
sha256:65a6c40035a2691cd980a8a48105e8312374edf0d8c1081778af7c6b32e6f511
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.11
14.1 MB
sha256:a92c5cd2560b047f830712d4aafe18ddba7a63d793d8bd9dee00953701ef80b4
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.12
14.1 MB
sha256:ca15a22fe4ce64ddb56e75e5876feb53c92fd211f3ea697258c7928150feb6b5
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.13
14.1 MB
sha256:0074aa4609b51d88d90278ececc2b1a376094d31381128d149af1b4912f68abe
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.14
14.1 MB
sha256:4db1d8d0d338b2392f11138abcd6dbda821d50e75f40ab750aa10b8051f7ba33
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.8
14.1 MB
sha256:24a9d825cda4063ab20aa32efeb503d7d7c9b66c4e73f61c6d14e74f0cf9c7f6
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_ARM64_Python3.9
14.1 MB
sha256:205b3e6572adb609f17aafc5ab30fd78755e9897239e5e5d7e7a173f4df7719d
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.10
14.5 MB
sha256:bbc50cd236c19cc5655c0313e464e8f8396ae59adb703b4b3e2600927f17532e
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.11
14.5 MB
sha256:e57c68329b0d0c0aa33bfc16d4addab57ede6313c514aed42fe0d8fadfadf41c
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.12
14.5 MB
sha256:854b134af7cb36b0bc7a8bf1cccb61d825c213bb4630beadb7c9d67d52c62efa
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.13
14.5 MB
sha256:423ed6ca64b9916b9b29dff4816e06aaf0eff86573c9b3bcfc901ee52ff34c46
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.14
14.5 MB
sha256:35dcc8155095455bc29d4c5e667c8e264b27d57e571b3bfb060cf3aee9da16bd
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.8
14.5 MB
sha256:ccd970db4b3652b74201d6863e5faabf1be0d556222fc5f958b9a64bfff23702
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-macOS_X64_Python3.9
14.5 MB
sha256:1581da8eaeb945f791d029a4ebeb6a352d0db77e31ec6b149e3e7bcd1f207aa8
wheel-27647581251-943face1daff34a97dab0c7f168fba380bc91597-sdist
302 KB
sha256:f076afab26bb3642167c8d811378f1d048726ac6a8b724ea470c3b230f680f8a