fix(verification): replace invalid UUID in verify-reviews workflow (#1906) #249
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-1906"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The
verify-reviewsworkflow atverification/workflow-verify-reviews.yamlfails to load with a UUID schema validation error on theidfield, silently blocking all pre-PR agent review verification runs.Root Cause
The workflow's
idfield was set toe5f6a7b8-9c0d-1e2f-3a4b-5c6d7e8f9a0b— a sequential hex placeholder created when the file was first added in commitdf42ce656. This value is not a valid RFC 4122 UUID:3, but the swamp workflow engine's UUID regex requires[89abAB](the RFC 4122 variant)/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|...)$/The workflow was never smoke-tested after creation (the test plan checkbox in the original PR was unchecked), so the invalid UUID went unnoticed.
Fix
Replace the placeholder with a valid UUID v4 (
94c0688e-1bf0-4f4b-b1b2-cb349e4abe36), generated viauuidgen. This is a one-line change to theid:field on line 1.Impact
SWAMP_WORKFLOWS_DIR=verification swamp workflow validate verify-reviewsfails — the engine logs "Skipping broken extension workflow" and the workflow is invisibleverify-reviewsis affected;verify-buildwas already valid (its UUIDa1b2c3d4-...has correct version/variant bytes)Why This Is Correct
The UUID v4
94c0688e-1bf0-4f4b-b1b2-cb349e4abe36satisfies all RFC 4122 constraints:4✓b(matches[89abAB]) ✓Verification
Closes #1906
Co-Authored-By: Paul Stack public@paulstack.co.uk
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com