Skip to content

[Actions] Auto-Update dependencies #72

[Actions] Auto-Update dependencies

[Actions] Auto-Update dependencies #72

Triggered via pull request May 1, 2025 00:35
Status Success
Total duration 1m 21s
Artifacts

test.yml

on: pull_request
actionlint
2s
actionlint
Check if automatic project update was successful
2s
Check if automatic project update was successful
pre-commit
1m 12s
pre-commit
docs
38s
docs
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (3.13): home/runner/.cache/pypoetry/virtualenvs/climate-data-v033_OfD-py3.13/lib/python3.13/site-packages/geopandas/_compat.py#L7
The 'shapely.geos' module is deprecated, and will be removed in a future version. All attributes of 'shapely.geos' are available directly from the top-level 'shapely' namespace (since shapely 2.0.0).
test (3.13): home/runner/.cache/pypoetry/virtualenvs/climate-data-v033_OfD-py3.13/lib/python3.13/site-packages/rasterra/_array.py#L8
numpy.core.multiarray is deprecated and has been renamed to numpy._core.multiarray. The numpy._core namespace contains private NumPy internals and its use is discouraged, as NumPy internals can change without warning in any release. In practice, most real-world usage of numpy.core is to access functionality in the public NumPy API. If that is the case, use the public NumPy API. If not, you are using NumPy internals. If you would still like to access an internal attribute, use numpy._core.multiarray.flagsobj.
test (3.12): home/runner/.cache/pypoetry/virtualenvs/climate-data-v033_OfD-py3.12/lib/python3.12/site-packages/geopandas/_compat.py#L7
The 'shapely.geos' module is deprecated, and will be removed in a future version. All attributes of 'shapely.geos' are available directly from the top-level 'shapely' namespace (since shapely 2.0.0).
test (3.12): home/runner/.cache/pypoetry/virtualenvs/climate-data-v033_OfD-py3.12/lib/python3.12/site-packages/rasterra/_array.py#L8
numpy.core.multiarray is deprecated and has been renamed to numpy._core.multiarray. The numpy._core namespace contains private NumPy internals and its use is discouraged, as NumPy internals can change without warning in any release. In practice, most real-world usage of numpy.core is to access functionality in the public NumPy API. If that is the case, use the public NumPy API. If not, you are using NumPy internals. If you would still like to access an internal attribute, use numpy._core.multiarray.flagsobj.