Skip to content

Bump prefix-dev/setup-pixi from 0.9.0 to 0.9.5 #2428

Bump prefix-dev/setup-pixi from 0.9.0 to 0.9.5

Bump prefix-dev/setup-pixi from 0.9.0 to 0.9.5 #2428

Triggered via pull request April 1, 2026 04:18
Status Success
Total duration 12m 0s
Artifacts 6

ci.yml

on: pull_request
should run ci
6s
should run ci
cache-pixi-lock
1m 7s
cache-pixi-lock
Matrix: integration-test
Matrix: unit-test
TypeChecking: pixi run typing
1m 3s
TypeChecking: pixi run typing
build-and-upload-nightly-parcels
1m 57s
build-and-upload-nightly-parcels
merge-test-artifacts
merge-test-artifacts
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
ty (invalid-return-type): src/parcels/_core/index_search.py#L46
src/parcels/_core/index_search.py:46:16: invalid-return-type: Return type does not match returned value: expected `tuple[int, int]`, found `tuple[Unknown, ndarray[tuple[Any, ...], dtype[Any]]]` src/parcels/_core/index_search.py:23:6: Expected `tuple[int, int]` because of return type info: rule `invalid-return-type` is enabled by default
ty (not-iterable): src/parcels/_core/fieldset.py#L484
src/parcels/_core/fieldset.py:484:26: not-iterable: Object of type `None` is not iterable info: It doesn't have an `__iter__` method or a `__getitem__` method info: rule `not-iterable` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L484
src/parcels/_core/fieldset.py:484:5: invalid-assignment: Too many values to unpack: Expected 2 src/parcels/_core/fieldset.py:484:26: Got 3 info: rule `invalid-assignment` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L423
src/parcels/_core/fieldset.py:423:22: invalid-assignment: Object of type `Dataset` is not assignable to `UxDataset` src/parcels/_core/fieldset.py:423:17: Declared type `UxDataset` info: rule `invalid-assignment` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L404
src/parcels/_core/fieldset.py:404:22: invalid-assignment: Object of type `Dataset` is not assignable to `UxDataset` src/parcels/_core/fieldset.py:404:17: Declared type `UxDataset` info: rule `invalid-assignment` is enabled by default
ty (unresolved-attribute): src/parcels/_core/fieldset.py#L357
src/parcels/_core/fieldset.py:357:175: unresolved-attribute: Attribute `left` is not defined on `None` in union `Unknown | TimeInterval | None` info: rule `unresolved-attribute` is enabled by default
ty (invalid-argument-type): src/parcels/_core/fieldset.py#L210
src/parcels/_core/fieldset.py:210:34: invalid-argument-type: Argument to bound method `__init__` is incorrect: Expected `UxDataArray`, found `DataArray` src/parcels/_core/uxgrid.py:21:9: info: Method defined here src/parcels/_core/uxgrid.py:21:44: Parameter declared here info: rule `invalid-argument-type` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L161
src/parcels/_core/field.py:161:20: unresolved-attribute: Attribute `zdim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L154
src/parcels/_core/field.py:154:20: unresolved-attribute: Attribute `ydim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L147
src/parcels/_core/field.py:147:20: unresolved-attribute: Attribute `xdim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
cache-pixi-lock
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
ty (redundant-cast): src/parcels/_core/xgrid.py#L379
src/parcels/_core/xgrid.py:379:24: redundant-cast: Value is already of type `Literal["X", "Y", "Z"]` info: rule `redundant-cast` is enabled by default
Unit tests: ubuntu | pixi run -e test tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-minimum tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-minimum tests
Cache save failed.
Unit tests: ubuntu | pixi run -e test-py313 tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-py313 tests
Cache save failed.
Unit tests: ubuntu | pixi run -e test-py311 tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-py311 tests
Cache save failed.
Unit tests: windows | pixi run -e test tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
Unittest report ubuntu-test
25.8 KB
sha256:cbf87ff3d84ac5795400a2d563fa774b4b19ae252e1a9befc9ccc3e5c1d201c4
Unittest report ubuntu-test-minimum
25.9 KB
sha256:1c65eac870f98534e8ff0754097ac5eb723190418396a56f018b4d837d48cf54
Unittest report ubuntu-test-py311
26.1 KB
sha256:6379d360f7ef7b8d2b99dd1ca9344d26e5caa9cbfda6562a0d303ee520ccd074
Unittest report ubuntu-test-py313
26.1 KB
sha256:4a9cfcb11df5d4c97fa5f4c0d42c7555d5b2e79f0fb4179f7d60d6e89170f245
Unittest report windows-test
26.3 KB
sha256:19a570891a36395a09bc1217553a2c94599f575415bc37a5b1ef46f43a33ef7c
pixi-lock
246 KB
sha256:6c40df95bc9ac7ff5fb8e743b1a6b0d14abdd914cd643437a2a0deb5ee743905