-
Notifications
You must be signed in to change notification settings - Fork 552
[CI] Add stable and latest tags #3826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
.github/workflows/mark-stable.yaml
Outdated
else | ||
echo "::error::Version tag v${{ github.event.inputs.version }} does not exist in the repository." | ||
exit 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the version doesn't exist, the previous step will fail in docker pull too, but I am not sure a docker pull failure will fail the step itself.
I suggest running the stable tag step first to ensure we fail fast if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can run them independently as it can be that for some reason one of tags somewhere isn't found(which is not likely, but technically is possible, so we can run again without thinking about the execution order)
During testing of my work I found out that if newest version contains workflow changes, github doesn't allow updating unless PAT is used:
|
📝 Description
This PR updates the CI as follows:
On every release, a latest tag will now be published alongside the versioned tag.
Introduces a new workflow for marking a GA version as stable.
This workflow re-tags the specified version’s images as stable, pushes them to the registry, and automatically opens a PR updating the stable badge in the README on GitHub. The PR description includes a note reminding maintainers to manually update the stable tag to the desired version. Manual action is required due to the issue described in #3826 (comment), where a Personal Access Token (PAT) is necessary for pushing changes that modify GitHub workflows.
✅ Checklist
🧪 Testing
gonna test after merge fully
🔗 References
🚨 Breaking Changes?