Skip to content

feat: plugin bundling, catalog, installation and versioning #134

feat: plugin bundling, catalog, installation and versioning

feat: plugin bundling, catalog, installation and versioning #134

Triggered via pull request May 5, 2026 19:31
Status Cancelled
Total duration 1m 5s
Artifacts

ci.yml

on: pull_request
Docs Build  /  Hugo Build
8s
Docs Build / Hugo Build
Matrix: Lint & Static Analysis / python-lint
Matrix: Lint & Static Analysis / syntax-check
Matrix: Tests / test
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 8 warnings
Lint & Static Analysis / jsonlint
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Lint & Static Analysis / ruff (cpex)
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Tests / Python 3.12
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Tests / Python 3.12
The operation was canceled.
Lint & Static Analysis / vulture (cpex)
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Lint & Static Analysis / vulture (cpex)
The operation was canceled.
Lint & Static Analysis / radon (cpex)
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Lint & Static Analysis / interrogate (cpex)
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Tests / Python 3.13
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Tests / Python 3.11
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Tests / Python 3.11
The operation was canceled.
CI
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
CI
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
CI
Canceling since a higher priority waiting request for CI-refs/pull/31/merge exists
Docs Build / Hugo Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peaceiris/actions-hugo@v3. 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/
Lint & Static Analysis / yamllint: ./tests/unit/cpex/fixtures/configs/isolated_plugin.yaml#L34
34:1 [empty-lines] too many blank lines (1 > 0)
Lint & Static Analysis / yamllint: ./tests/unit/cpex/fixtures/configs/isolated_plugin.yaml#L26
26:7 [indentation] wrong indentation: expected 4 but found 6
Lint & Static Analysis / yamllint: ./tests/unit/cpex/fixtures/configs/isolated_plugin.yaml#L15
15:3 [indentation] wrong indentation: expected 0 but found 2
Lint & Static Analysis / ruff (cpex)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
Lint & Static Analysis / vulture (cpex)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
Lint & Static Analysis / radon (cpex)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
Lint & Static Analysis / interrogate (cpex)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/