openshift-cli 4.9

[anothertobi]

The upstream repository changed from tag-based versioning to branch-based versioning. Further, the Makefile was changed upstream and therefore this updates the patch enabling darwin-arm64 builds.

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[SMillerDev]

Please make a new pull request upstream with the changed makefile then.

[anothertobi]

Please make a new pull request upstream with the changed makefile then.

There are no other changes required in the Makefile besides openshift/oc#889. It's just the merge result that changed, and therefore the patch isn't up-to-date. That's why I replaced it with the output of gh pr diff https://github.com/openshift/oc/pull/889 --patch (only surrounding lines changed, but the ones starting with + are the same).

[carlocab]

A branch is a moving target, which makes these builds non-reproducible, which we shouldn't have. Why have upstream stopped tagging releases?

[anothertobi]

Not sure why exactly they stopped tagging releases. I suspect that they are doing global releases, with one version across all repos relevant for OCP4, and reference the latest commits of the branches for that release in a global configuration.

This is an automated issue mentioning which branches are frozen for the "global" release: openshift/oc#180

Nevertheless, I updated the PR to point to the latest commit of the release-4.9 branch, which is the latest stable branch for OCP4. This makes the builds reproducible.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[SMillerDev]

Since this strategy goes against our acceptable formulae requirements we can not accept this change. Unless upstream has some sort of tagged versions I think we'll have to deprecate the formula instead.