-
Notifications
You must be signed in to change notification settings - Fork 105
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
master and release-4.16 still point to 4.15 versions #879
Comments
Hi, I didn't find any quick way to automate that. Do you have any suggestion to tackle this? |
@liornoy did something for metallb to automatically create prs to bump version. Perhaps, we could do something similar. |
Yes, the bump_metallb.yaml workflow we've implemented runs twice a day to fetch the latest Metallb. If there's a newer commit, it automatically executes scripts to update the manifests and files a pull request that includes informative details about both the old and new commits. |
AFAIK, |
I do not think there is a way to automate this as we don't have github actions here maybe something in the openshift-ci can do it but again, I'm not sure. I would like to have at least an entry in the d/s Makefile where we have a version that we can update with a |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@zeeke, any plans to automate what you did in #840?
The text was updated successfully, but these errors were encountered: