The wait-for-chains task extracts just the logIndex number from the Rekor transparency URL (e.g. 1732077376), but the draft release template expects the full hex entry UUID (e.g. 108e9186e8c5677a...).
This causes the draft release attestation section to contain a bare number instead of the proper UUID, making the rekor-cli get --uuid commands non-functional.
Fix: Fetch the actual UUID from the Rekor API, falling back to logIndex if the API call fails.
See tektoncd/pipeline#10203 for the pipeline fix.
/kind bug
The
wait-for-chainstask extracts just thelogIndexnumber from the Rekor transparency URL (e.g.1732077376), but the draft release template expects the full hex entry UUID (e.g.108e9186e8c5677a...).This causes the draft release attestation section to contain a bare number instead of the proper UUID, making the
rekor-cli get --uuidcommands non-functional.Fix: Fetch the actual UUID from the Rekor API, falling back to logIndex if the API call fails.
See tektoncd/pipeline#10203 for the pipeline fix.
/kind bug