Skip to content

ci: add scheduled runs for release branches - #5393

Merged
kolyshkin merged 1 commit into
opencontainers:mainfrom
kolyshkin:scheduled
Aug 19, 2026
Merged

ci: add scheduled runs for release branches#5393
kolyshkin merged 1 commit into
opencontainers:mainfrom
kolyshkin:scheduled

Conversation

@kolyshkin

Copy link
Copy Markdown
Contributor

Somehow we missed adding release-1.4 and release-1.5 branches to scheduled CI runs (added in commit 995a39a).

AFAIR this does not need to be backported (scheduled jobs are only run on main branch).

Somehow we missed adding release-1.4 and release-1.5 branches to
scheduled CI runs (added in commit 995a39a).

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

@thaJeztah thaJeztah left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@thaJeztah

Copy link
Copy Markdown
Member

This needs to be cherry-picked as well for it to be applied to each of those branches).

@kolyshkin

Copy link
Copy Markdown
Contributor Author

This needs to be cherry-picked as well for it to be applied to each of those branches).

I think this doesn't work like this (and I already explained why in PR description above, as well as in the yml file itself).

@lifubang lifubang left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM with one suggestion, and I think we can implement it in a follow-up PR.

strategy:
matrix:
branch: ["main", "release-1.3"]
branch: ["main", "release-1.5", "release-1.4", "release-1.3"]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

One thing to consider: the branch matrix is hardcoded, so every time we cut a new minor release we'll need to remember to update this list (e.g. when 1.6 is released: add release-1.6, drop release-1.3 which falls out of support per RELEASES.md). To avoid forgetting that, two suggestions:

  1. Add a reminder comment in this file;
  2. we could make the matrix dynamic: a prep job lists the repo branches via the GitHub API, picks the 3 newest release-X.Y branches (matching the latest / latest-1 / latest-2 policy), and feeds them to the matrix.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@lifubang makes sense; opened #5412 as a followup

@kolyshkin
kolyshkin merged commit 76d9cf5 into opencontainers:main Aug 19, 2026
56 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants