fix(release): use pipeline scripts for candidate lock verification - #720
fix(release): use pipeline scripts for candidate lock verification#720guibeira wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
guibeira
added
no-ticket
1 participant
Summary
Use the pipeline checkout when verifying the registry lock during candidate smoke tests.
Root cause
Alpha releases dispatch the current release workflow from
mainwhile building the worker source from the release tag. The lock verifier was invoked from the tag checkout, so alpha tags created before that script was added failed withNo such file or directory. The workflow already checks out the current pipeline sources underpipeline-scripts; this change uses that copy consistently with the interface collector.Impact
Candidate validation can verify alpha releases created from feature branches even when their tags do not contain the latest release validation scripts.
Validation
.github/workflows/_candidate-smoke.ymlwith the workspace YAML parsergit diff --checkpipeline-scriptscheckout onmainactionlintcould not be run because the container image registry timed out during download.