chore(ci): inline PyPI publishing workflows to resolve attestation issues#12
Merged
Conversation
Contributor
CI Development Pipeline Status✅ Pipeline: Completed successfully. View Run Details |
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
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.
Description
This PR refactors the project's PyPI publishing configuration to resolve issues with GitHub artifact attestations. The nested
_publish.ymlreusable workflow was removed, and theactions/attest-build-provenance,pypa/gh-action-pypi-publish, and GitHub Release creation steps were directly integrated into thenightly.ymlandrelease.ymlworkflows. This structural change removes the nested job dependency, ensuring that the provenance action can correctly identify and verify the built artifacts without identity mismatches.Additionally, workflow titles and internal file descriptions across the
.github/workflowsdirectory have been simplified for better readability (e.g., from "CI — Nightly Deep Dive" to "CI — Nightly").Type of Change
README.md,SUPPORT.md, docstrings, etc.)Test Plan
These changes strictly impact the GitHub Actions infrastructure. Verification will rely on observing the completion of the modified workflows in the target repository, specifically verifying that the
actions/attest-build-provenancestep innightly.ymlandrelease.ymlexecutes successfully without identity errors during publishing.Related Issues
Screenshots / Visuals (if applicable)
N/A
Use of AI
## WRITTEN BY AI ##)Checklist
Important
Please review and complete this checklist before submitting your PR. This helps our maintainers process your contribution faster and ensures it meets the quality standards of
gitversioned.gitversioned.