Skip to content

fix(release): promote project version after attestation push#2807

Merged
jiparis merged 3 commits intochainloop-dev:mainfrom
jiparis:jiparis/product-release-status
Mar 2, 2026
Merged

fix(release): promote project version after attestation push#2807
jiparis merged 3 commits intochainloop-dev:mainfrom
jiparis:jiparis/product-release-status

Conversation

@jiparis
Copy link
Member

@jiparis jiparis commented Mar 2, 2026

Summary

  • Move the "Promote Chainloop Project Version" step from the release job to the finish_attestation job so it runs after chainloop attestation push, not before
  • Pass the current project version as a job output from release to finish_attestation
  • Remove the attestation phase tag from the failing contract

Closes #2805

Move the "Promote Chainloop Project Version" step from the release job
to the finish_attestation job, ensuring it runs after chainloop
attestation push. This prevents policy evaluations during push from
referencing the renamed version instead of the original one.

Closes chainloop-dev#2805

Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
@jiparis jiparis requested review from javirln and migmartri March 2, 2026 16:31
@kusari-inspector
Copy link

kusari-inspector bot commented Mar 2, 2026

Kusari Inspector

Kusari Analysis Results:

Proceed with these changes

✅ No Flagged Issues Detected
All values appear to be within acceptable risk parameters.

No pinned version dependency changes, code issues or exposed secrets detected!

Note

View full detailed analysis result for more information on the output and the checks that were run.


@kusari-inspector rerun - Trigger a re-analysis of this PR
@kusari-inspector feedback [your message] - Send feedback to our AI and team
See Kusari's documentation for setup and configuration.
Commit: c2cc912, performed at: 2026-03-02T16:37:44Z

Found this helpful? Give it a 👍 or 👎 reaction!

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/release.yaml">

<violation number="1" location=".github/workflows/release.yaml:231">
P2: Potential script injection: `${{ needs.release.outputs.current_version }}` is interpolated directly in a `run:` block. GitHub's security hardening guide recommends passing expressions through `env:` to prevent injection if the value contains shell metacharacters.

Use an intermediate environment variable instead of direct interpolation.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Pass needs.release.outputs.current_version and github.ref_name through
env variables instead of interpolating them directly in the run block.

Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
@kusari-inspector
Copy link

Kusari PR Analysis rerun based on - c2cc912 performed at: 2026-03-02T16:37:44Z - link to updated analysis

Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
@jiparis jiparis merged commit 3facd4e into chainloop-dev:main Mar 2, 2026
15 checks passed
@jiparis jiparis deleted the jiparis/product-release-status branch March 2, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: project version is being renamed before finishing the attestation

2 participants