Skip to content

Conversation

@universal-itengineer
Copy link
Member

@universal-itengineer universal-itengineer commented Dec 9, 2025

Description

Fix check release on channels (fix PR #1720)

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

Changed credentials for the channel version check step.

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: fix
summary: fix check release on channels

Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
@universal-itengineer universal-itengineer force-pushed the fix/ci/check-release-on-channels branch from 3cc8a36 to b518f60 Compare December 9, 2025 16:10
@universal-itengineer universal-itengineer added this to the v1.3.0 milestone Dec 9, 2025
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
@universal-itengineer universal-itengineer force-pushed the fix/ci/check-release-on-channels branch from 1a1d490 to c715c17 Compare December 10, 2025 08:37
@universal-itengineer universal-itengineer marked this pull request as ready for review December 10, 2025 08:38
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
@universal-itengineer universal-itengineer merged commit b517ccb into main Dec 10, 2025
37 of 38 checks passed
@universal-itengineer universal-itengineer deleted the fix/ci/check-release-on-channels branch December 10, 2025 12:29
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