feat: add reusable Python package candidate module - #38
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: add a reusable, closed-surface Dagger Lego for building and verifying Python wheel/sdist candidates without publishing them.
Why: edgeproc-core, edge-proc, and Assay currently duplicate locked build, artifact validation, and candidate evidence logic. This module centralizes the source/token/provider-free candidate boundary while leaving OIDC publication to the official PyPA action and requiring a fresh release decision.
Public API: build, candidate, dependency-audit, verify-candidate. There are no command, image, path, tag, registry, OIDC, or publisher escape inputs.
Proof: 128 module tests at 96.93% coverage and 91.5% branches; 219 root tests at 96.38%; full 67-case wheel/sdist archive matrix; Ruff, strict mypy, Xenon A, audits, schema, generated Python/TypeScript clients, real EdgeProc-core wheel+sdist/Twine validation, and SDK-free bootstrap all green. Independent feature and post-rebase reviews are Ready Yes.