fix(ci): missing CHAINLOOP_PROJECT_NAME env var in release workflow #2572
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Promote Chainloop Project Version step was missing the CHAINLOOP_PROJECT_NAME environment variable, causing the project version update command to fail during releases. This variable was defined in the init_attestation job but not propagated to the release job where it's needed. Signed-off-by: Miguel Martinez <miguel@chainloop.dev>
migmartri
changed the title
jiparis
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes missing environment variable in the release workflow that was causing the project version promotion step to fail during releases.
Changes
CHAINLOOP_PROJECT_NAME: "chainloop"environment variable to the "Promote Chainloop Project Version" stepinit_attestationjob but was not available in thereleasejob where the project version update command runsImpact
Without this fix, the
chainloop project version updatecommand would fail because${CHAINLOOP_PROJECT_NAME}was undefined, preventing proper renaming of pre-release versions to actual release versions.