Skip to content

ci: update the code review action to keep security weaknesses out of findings - #6629

Merged
peholmst merged 1 commit into
mainfrom
ci/code-review-ae1f782
Nov 11, 2026
Merged

peholmst merged 1 commit into
mainfrom
ci/code-review-ae1f782

Conversation

@totally-not-ai

@totally-not-ai totally-not-ai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Review risk: two-way door — only the PR code-review workflow; revert the one-line pin to go back.

Summary

Updates the pinned vaadin/github-actions/code-review action from 5e91962 to the current main (ae1f782). This picks up vaadin/github-actions#34 (a security area in the code review prompt) and vaadin/github-actions#35 (neither the code nor the docs review reports or hints at a pre-existing security weakness, since findings are public).

What changed

  • .github/workflows/code-review.yml: action pin 5e91962 → ae1f782. No inputs changed.

Test summary

  • actionlint on the workflow (no new findings).

Working on behalf of Artur

…findings

Pins vaadin/github-actions/code-review to ae1f782. The code review now
has a security area, and neither profile reports or hints at a
pre-existing security weakness, since findings are public.
@peholmst
peholmst marked this pull request as ready for review November 11, 2026 14:10
@peholmst peholmst added the target/v25.3 Automatically cherry-pick to the v25.3 branch label Nov 11, 2026
@peholmst
peholmst merged commit ba657fe into main Nov 11, 2026
16 of 17 checks passed
@peholmst
peholmst deleted the ci/code-review-ae1f782 branch November 11, 2026 14:11

@vaadin-review-bot vaadin-review-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Nothing to flag — the changes look good.

@vaadin-bot

Copy link
Copy Markdown
Contributor

Hi @totally-not-ai[bot] and @peholmst, when i performed cherry-pick to this commit to v25.3, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick ba657fe
error: could not apply ba657fe... ci: update the code review action to keep security weaknesses out of findings (#6629)
hint: After resolving the conflicts, mark them with
hint: "git add/rm ", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

need to pick manually v25.3 target/v25.3 Automatically cherry-pick to the v25.3 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants