Repository navigation
Separate Python package publishing, testing, and attestation - #8546
Draft
Amaury Chamayou (achamayou) wants to merge 5 commits into
Draft
Amaury Chamayou (achamayou) wants to merge 5 commits into
Amaury Chamayou (achamayou) wants to merge 5 commits into
Conversation
Use the latest published SDK only in CCF release-build tests. Remove the legacy GitHub publisher and wheel release assets, and dispatch a digest-bound Python attestation from OneBranch after ESRP publication. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Avoid reinstalling the SDK in caller-owned virtual environments shared by release-test sandboxes. Cover inherited environments with regression cases while retaining published SDK installation in sandbox-owned environments. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the OneBranch-to-GitHub dispatch stage and its credential requirement. Document manual attestation from the release tag using the original build inputs, and print the package version and wheel digest for maintainers. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This branch has not been deployed
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.
Motivation
Follow up on #8501: Python packages will be released separately through the manually queued OneBranch pipeline. Remove the competing GitHub Actions publisher and keep release testing and Python attestations consistent with that split.
Implementation summary
python-package.attestation.sigstore.json.Safety and compatibility
No CCF runtime, protocol, or ledger-format changes. The GitHub Release review/publication gate, NPM publisher, and default development/CI SDK selection are preserved. Release builds intentionally test the already-published SDK rather than an unpublished local version.
Attestation is manually triggered in GitHub; no additional GitHub credential or dispatch job is needed in OneBranch. The attestation workflow must exist on
mainand the release tag. See the OneBranch release documentation for manual invocation and attestation-only retry instructions.The Python attestation signs the verified published wheel; it does not claim that GitHub Actions built it or replace build-time OneBranch provenance. The end-to-end process still needs validation with a production OneBranch publication and manual attestation.
Local repository checks and release-mode recovery/logging tests passed. With
LONG_TESTS=ON,cd build && ./tests.sh --output-on-failure -R '^lts_compatibility$' --no-tests=errorfails with HTTP 500 during CCF 6.0.28 private ledger recovery. The same failure reproduces with the editable local SDK and the released SDK; this unrelated compatibility failure is not changed here.