Description

Follow-up to the 23 May 2024 community call, usually the release for 1.6/1.7 will occur simultaneously; however, this isn't guaranteed. The issue observed is if a new cut of 1.6 occurs after the 1.7 cut, then the 1.6 release will be marked latest which can break some downstream automation which are watching the latest tag.

Steps to reproduce the issue

1. cut 1.7 release
2. cut 1.6 release
3. 1.6 will be marked latest

Describe the results you received and expected

If 1.6 release is cut after 1.7, then the 1.6 release will be marked latest. Maintainers have been manually marking the 1.7 release latest; however, it would be nice if the release automation can handle this without needing to manually mark the release latest.

One approach is to use make_latest: false in the release/1.6 branch and make_latest: true in the release/1.7 branch in the release workflow's action-gh-release package. The trade-off is the release candidates from mainline will not be marked latest; however, this should be a reasonable behavior.

What version of containerd are you using?

n/a

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response