Skip to main content

cf_pipeline_sdk

cf_pipeline_sdk packages the native step-runtime contract provider owned by the pipeline SDK package:

  • the Python module cogniflow_pipeline_sdk
  • the native CfStepRuntimeContractV1 provider surface consumed by cf_pipeline_engine

Published distribution name:

pip install cf-pipeline-sdk

Scope

The published distribution name is cf-pipeline-sdk. The Python import package remains cogniflow_pipeline_sdk.

The engine resolves the packaged runtime provider through the provider registry and package descriptor, not via SDK Python helper APIs.

Step build tooling, siggen, and validation-spec generation live in cf-step-tooling.

Validation Spec Output

cf_step_tooling.validation.generate_validation_spec(...) keeps the existing normalized port fields unchanged:

  • id
  • key
  • types
  • name
  • multi for input ports

When a step manifest port declares cf:valueContract, the generated port entry now adds a value_contract object with additive metadata:

  • shape_kind
  • element_types
  • table_schema.columns[] with name, type, and nullable when a table schema is declared

cf:valueContract is the only supported typed-contract source for validation spec generation.

Native build prerequisites

The SDK is built with scikit-build-core and CMake.

For Windows publish/preflight runs, use:

  • CPython 3.14
  • CMake on PATH
  • a working Windows C++ toolchain compatible with that CMake installation

The CI publish workflow targets windows-latest. If your local machine exposes multiple CMake/compiler combinations, keep the selected CMake and compiler toolchain consistent for the whole build.

Publishing

cf_pipeline_sdk is published with the dedicated Windows workflow:

  • Workflow: .github/workflows/cf_pipeline_sdk_windows_publish.yml
  • Package directory: sandcastle/cf_pipeline/cf_pipeline_sdk
  • PyPI tag: cf-pipeline-sdk-v<version>
  • TestPyPI tag: cf-pipeline-sdk-v<version>-test

Local preflight:

powershell -ExecutionPolicy Bypass -File scripts/mimic_windows_python_publish_workflow.ps1 `
  -WorkflowFile .github/workflows/cf_pipeline_sdk_windows_publish.yml `
  -PackageDir sandcastle/cf_pipeline/cf_pipeline_sdk `
  -PythonExe py `
  -PythonVersion 3.14

Queue a dry-run dispatch:

powershell -ExecutionPolicy Bypass -File scripts/queue_windows_python_publish_workflow.ps1 `
  -WorkflowFile .github/workflows/cf_pipeline_sdk_windows_publish.yml `
  -PackageDir sandcastle/cf_pipeline/cf_pipeline_sdk `
  -PublishTarget testpypi `
  -Ref main `
  -RequireLocalPass `
  -DryRun

Metadata

Release files for cf-pipeline-sdk 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cf-pipeline-sdk 0.2.3
File Size Uploaded Provenance Actions
cf_pipeline_sdk-0.2.3.tar.gz 4.0 kB Without provenance Details for cf_pipeline_sdk-0.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cf-pipeline-sdk 0.2.3
File Interpreter ABI Platform Actions
cf_pipeline_sdk-0.2.3-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for cf_pipeline_sdk-0.2.3-cp314-cp314-win_amd64.whl

Total release size: 15.9 kB

Release files / cf_pipeline_sdk-0.2.3.tar.gz

Download URL cf_pipeline_sdk-0.2.3.tar.gz
Size 4.0 kB
Tags Source
SHA-256 checksum
How to use checksums
8b16b67325bbe04ec12e58a6d74e567fcd68cb04cb9709ba610c30386281ca90
BLAKE2b-256 checksum
How to use checksums
e635848f8b7197f81c4c9e8816f625251290a5180af9ee0a22a185f8cc73600d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.14.4

Release files / cf_pipeline_sdk-0.2.3-cp314-cp314-win_amd64.whl

Download URL cf_pipeline_sdk-0.2.3-cp314-cp314-win_amd64.whl
Size 11.8 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
7258af56f8c943b18e2f4804b9777e255a598ab5951332062d643a7de26c58bd
BLAKE2b-256 checksum
How to use checksums
d0d42492e8d6c6095cbcc4a5aa10cd30b0d1343c2939d0a460eadbf7e80919fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.14.4

Security for cf-pipeline-sdk 0.2.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page