master and release-4.16 still point to 4.15 versions

[mlguerrero12]

@zeeke, any plans to automate what you did in #840?

[zeeke]

Hi, I didn't find any quick way to automate that. Do you have any suggestion to tackle this?

[mlguerrero12]

@liornoy did something for metallb to automatically create prs to bump version. Perhaps, we could do something similar.

[liornoy]

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.

[zeeke]

AFAIK, openshift/* repositories do not run github actions. BTW, if you have any good idea, feel free to open a PR.

[SchSeba]

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 bump bundle or something like that.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.