Add safeguard for Github's eventual consistency in container release process
Open
@poikilotherm is already working on this.
Since Jul 2, 2026.
Component: Containers
Size: 3
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
If the scheduled maintenance process is triggered by a release being done, add a safeguard to verify the release number is in the list of discovered supported releases.
As part of the 6.11 release we saw that the API did not return 6.11 also it triggered the CI run.
We can fail fast by comparing the env var carrying the release number string with the JSON array's content.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.