Skip to content

build(deps): bump types-requests from 2.32.4.20250809 to 2.32.4.20250913 #4404

build(deps): bump types-requests from 2.32.4.20250809 to 2.32.4.20250913

build(deps): bump types-requests from 2.32.4.20250809 to 2.32.4.20250913 #4404

Triggered via pull request September 15, 2025 17:18
Status Failure
Total duration 1h 20m 45s
Artifacts

ci.yml

on: pull_request
Matrix: Conda Build
Matrix: Build
Matrix: Stable
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 11 warnings, and 11 notices
Build (windows-latest, 3.10, firefox)
Process completed with exit code 1.
Stable (ubuntu-latest, chrome)
Process completed with exit code 1.
Build (ubuntu-latest, 3.12, chromium)
Process completed with exit code 1.
Build (windows-latest, 3.9, firefox)
Process completed with exit code 1.
Conda Build (macos-13)
Process completed with exit code 1.
Stable (macos-latest, msedge)
Process completed with exit code 1.
Stable (macos-latest, chrome)
Process completed with exit code 1.
Build (macos-latest, 3.9, webkit)
Process completed with exit code 1.
Build (macos-latest, 3.9, firefox)
Process completed with exit code 1.
Build (macos-latest, 3.9, chromium)
Process completed with exit code 1.
Conda Build (ubuntu-22.04)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Conda Build (ubuntu-22.04)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Conda Build (ubuntu-22.04)
/home/runner/miniconda3/lib/python3.13/site-packages/conda/base/context.py:211: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.9. To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels: conda config --add channels defaults For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html deprecated.topic(
Conda Build (windows-2022)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Conda Build (windows-2022)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Conda Build (windows-2022)
C:\Users\runneradmin\miniconda3\Lib\site-packages\conda\base\context.py:211: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.9. To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels: conda config --add channels defaults For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html deprecated.topic(
Conda Build (windows-2022)
Terminal profiles are not available for system level installs
Conda Build (windows-2022)
Terminal profiles are not available for system level installs
Conda Build (macos-13)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Conda Build (macos-13)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Conda Build (macos-13)
/Users/runner/miniconda3/lib/python3.13/site-packages/conda/base/context.py:211: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.9. To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels: conda config --add channels defaults For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html deprecated.topic(
Build (windows-latest, 3.10, firefox)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.9, firefox)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.10, chromium)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.13, chromium)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.12, chromium)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.11, chromium)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.10, webkit)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.9, webkit)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Stable (windows-latest, chrome)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build (windows-latest, 3.9, chromium)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Stable (windows-latest, msedge)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677