Add one-click release workflow for cuda-pathfinder#1626
Open
cpcloud wants to merge 1 commit intoNVIDIA:mainfrom
Open
Add one-click release workflow for cuda-pathfinder#1626cpcloud wants to merge 1 commit intoNVIDIA:mainfrom
cpcloud wants to merge 1 commit intoNVIDIA:mainfrom
Conversation
Automates the manual release checklist into a single workflow_dispatch that takes a version number. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
rparolin
added
awaiting-response
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
2 participants
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.
Replaces the manual release checklist for cuda-pathfinder with a single
workflow_dispatchthat takes a version number.Pipeline
prepare→docs→publish-testpypi→verify-testpypi→publish-pypi→verify-pypi→finalizeupload-assetsruns in parallel with the publish chain (attached to the draftrelease with
--clobber).The verify jobs install the package in a fresh venv and assert
__version__matches -- replacing the manual
pip install+ import step. If TestPyPIverification fails, PyPI publish never runs.
Notable choices
ci/tools/lookup-run-idandci/tools/download-wheelsunmodifiedworkflow_dispatchinputs flow throughenv:to prevent shell injection