ci: compose reusable Python release foundations - #62
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhrjTokoEF6Zax8EASdGsv
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: compose EdgeProc CI with exact shared Foundation and Python-package Legos at central SHA 95c72573, preserving every existing release-candidate and PyPI publication boundary.
Why: the repository duplicated hosted source/scanner/audit/build verification. The adapter now derives exact green-main identity internally, binds the public source and full history, and delegates locked candidate validation to the central module.
No release workflow, publish workflow, product, dependency, version, tag, registry, secret, or environment changes. No publication is performed.
Proof: module 10/10; repository 472/472 at 98.40%; pinned Linux Dagger quality 472/472; Ruff, format, strict mypy, Xenon A, actionlint, locks, schema, Twine, and independent review green. Exact current-main candidate correctly fails closed because v0.4.1 is tagged to an older commit.