This release is a pre-release and may not be stable for production use.
Pyplines CLI standard
Shared inspection services and views derive Distribution and Action descriptions from canonical content, with explicit verification states.
pyplines-cli-common provides the shared Typer application boundary, safe
errors, and presentation used by the CLI and Builder. It has no Server dependency.
Human output is the default. AUTOMATION_MODE=enabled or --json selects
automation output: one JSON result on stdout, JSON errors and progress on stderr,
and no interactive prompts. Log-stream commands emit newline-delimited JSON.
Empty invocation and help show readable help and exit zero without credentials.
Redirecting stdout does not change the output format.
Exit codes: 0 success, 1 operation failure, 2 invalid usage/input, 3 observation timeout, 130 interruption. Unexpected exceptions never print arbitrary exception values; optional diagnostics identify their type without leaking tokens or signed URLs.
Human errors are concise stderr diagnostics without appended recovery commands.
Verbose mode exposes safe structured details; JSON errors use the ApiError
contract (code, message, optional correlationId, violations, details).
See CLI error diagnostics.
The shared package follows the release's CalVer version and is published before
CLI and Builder. Configure its PyPI Trusted Publisher for repository
pyplines/pyplines, workflow publish-release.yml, environment pypi.
Distribution tooling
Both operator CLI and builder import the same bounded archive reader, canonical writer, signature verifier, offline schema snapshot, and OCI registry transport. The signing source URI identifies publisher authority without requiring an Index. Registry transport is independent of publisher verification and never uses a Docker daemon. Dependencies and schemas ship in the common wheel.
The manual qualify-distribution-oci.yml workflow tests real registry transfer,
ORAS copying, and installed wheels. Its optional GHCR job publishes unique test
packages under the repository owner's qualification namespace and leaves them
for inspection; it does not run on pushes or releases automatically.
1 maintainer
Metadata
1 maintainer
Release files for pyplines-cli-common 2026.9.14a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyplines_cli_common-2026.9.14a1.tar.gz | 66.4 kB | With provenance | Details for pyplines_cli_common-2026.9.14a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyplines_cli_common-2026.9.14a1-py3-none-any.whl | Python 3 | none | any | Details for pyplines_cli_common-2026.9.14a1-py3-none-any.whl |
Total release size: 133.2 kB
Release files / pyplines_cli_common-2026.9.14a1.tar.gz
| Download URL | pyplines_cli_common-2026.9.14a1.tar.gz |
|---|---|
| Size | 66.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3acfc5e436b6d9e84d59a28493c6377d10ba19271a5c479634c331f8fac121cd
|
|
BLAKE2b-256 checksum How to use checksums |
a9bab22d55a5aa703deb183c1c3e2817722e0773f802e193288edf362691e401
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / pyplines_cli_common-2026.9.14a1-py3-none-any.whl
| Download URL | pyplines_cli_common-2026.9.14a1-py3-none-any.whl |
|---|---|
| Size | 66.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8907497d0de2936868956024d81053558f9a1b341f94df61bb994f1e8d79087
|
|
BLAKE2b-256 checksum How to use checksums |
066a7c2b5018bfe6b5f8e8296cf47dcbd955f00790737fcee3aa562641514044
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logSecurity for pyplines-cli-common 2026.9.14a1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyplines_cli_common-2026.9.14a1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logA 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.
