Skip to content

Conversation

@nevermarine
Copy link
Collaborator

Description

Run weekly svace build & analyze workflow on latest CSE release branch.

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: Run svace on latest CSE release branch.

@nevermarine nevermarine added this to the v1.4.0 milestone Dec 16, 2025
Signed-off-by: Maksim Fedotov <[email protected]>
@nevermarine nevermarine marked this pull request as ready for review December 16, 2025 14:43
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
Signed-off-by: Maksim Fedotov <[email protected]>
@nevermarine nevermarine merged commit cb5ecfb into main Dec 16, 2025
27 of 28 checks passed
@nevermarine nevermarine deleted the chore/ci/run-svace-on-latest-cse branch December 16, 2025 15:37
@nevermarine nevermarine mentioned this pull request Dec 22, 2025
4 tasks
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.

3 participants