You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: require explicit tag input for cuda-pathfinder release workflow (#1668)
* ci: require existing cuda-pathfinder tag in release workflow
Use a single explicit tag input for releases and validate both format and branch reachability before proceeding. This prevents the workflow from creating new tags and ensures releases are tied to pre-existing refs.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci: simplify cuda-pathfinder release tag handling
Resolve the release input directly as an explicit tag ref in checkout and require gh release creation to verify that tag exists. This removes redundant git validation plumbing while still preventing the workflow from creating tags implicitly.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci: remove manual tag format check in pathfinder release workflow
Rely on checkout of the explicit tag ref and gh release --verify-tag for existence checks, reducing workflow-specific validation logic while preserving no-tag-creation behavior.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
0 commit comments