Skip to content

PyIngestKit v1.0.0 - Stable Framework Contract

Latest

Choose a tag to compare

@tawounfouet tawounfouet released this 06 Sep 06:42
· 7 commits to main since this release
8886dfa

PyIngestKit 1.0.0 - Stable Framework Contract

Status: stable (publication is gated on successful post-merge qualification of the exact stable SHA).

PyIngestKit 1.0.0 promotes the fully qualified V1 release candidate to the first protected 1.x
compatibility line. It adds no new provider or orchestration capability at the version transition.

Release lineage

Stable promotion starts from the post-merge-qualified RC1 baseline:

e98a12cc3bbfb634d2fd2257f43049fa1e0333dd

The immutable v0.6.0 release remains the executable historical upgrade baseline.

Stable contents

  • framework package version 1.0.0;
  • maintained demo package version 1.0.0;
  • governed V1 Python public API promoted from stable-candidate to stable 1.x contract;
  • explicitly experimental surfaces kept outside the 1.x promise;
  • deterministic plugin discovery and failure isolation;
  • fail-closed configuration/profile resolution and explicit workspace precedence;
  • canonical error/deprecation behavior;
  • governed CLI commands, exit-code classes and successful JSON semantics;
  • governed logging/redaction behavior;
  • logical persistence and portable schema compatibility contracts;
  • immutable RAW, deterministic versioning/diff/publication and strict replay;
  • PostgreSQL persistence targets and metadata;
  • S3-compatible artifact/version storage;
  • five representative pilots covering nine maintained reference jobs;
  • Python 3.11/3.12/3.13 qualification;
  • PostgreSQL 16, MinIO/S3 and cross-host object-storage E2E qualification.

Upgrade evidence

The stable release-check creates real V0.6 versioned run history, versions and publication state from
the exact v0.6.0 tag, upgrades the same isolated environment to the built 1.0.0 wheels and proves:

  • historical run state remains readable;
  • historical DatasetVersion snapshots remain readable;
  • PublishedDataset still points at the historical V2 run;
  • strict replay succeeds from historical RAW without live reacquisition;
  • expected and actual fingerprints equal the historical published fingerprint.

Stable compatibility promise

All surfaces classified PUBLIC_STABLE_CANDIDATE by the historical A1 inventory and retained through
A2/B1/B2/RC1 are promoted to PUBLIC_STABLE for 1.x. Explicit experimental surfaces remain
experimental.

Stable public paths follow the documented deprecation policy and are retained throughout 1.x unless an
explicitly documented security/correctness emergency requires exceptional action.

Stable distributions

pyingestkit-1.0.0-py3-none-any.whl
pyingestkit-1.0.0.tar.gz
pyingestkit_demo_jobs-1.0.0-py3-none-any.whl
pyingestkit_demo_jobs-1.0.0.tar.gz
SHA256SUMS

CI groups release evidence as:

pyingestkit-v1.0.0-source
pyingestkit-v1.0.0-dist

Release governance

The stable v1.0.0 tag is not created on an unmerged release branch. It is created as an annotated,
immutable tag only after the stable PR is merged with a merge commit and the exact merge SHA passes
post-merge CI and Security. Final release assets and checksums are then published from that qualified
lineage.

The historical v0.6.0 tag and RC1 evidence remain unchanged.