fix: fetch full Rekor UUID instead of logIndex in wait-for-chains
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the wait-for-chains task and the code that parses the Rekor transparency URL, then inspect the draft release template and the related pipeline fix in tektoncd/pipeline#10203. Update the UUID lookup to use the Rekor API with logIndex fallback, and verify that generated rekor-cli get --uuid commands use the full UUID when available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100