Rui Chen

nope, let me check on it.

@SimeonEhrig what patch tag should I use for clang and llvm?

for clang, here are the release tags I saw ``` $ git tag -l | grep cling-patches cling-patches-is-missing-making-all-static-init cling-patches-minimal-rebase-pre-FIXUP cling-patches-r191429 cling-patches-r199798 cling-patches-r201395 cling-patches-r202469 cling-patches-r210169 cling-patches-r214395 cling-patches-r214630 cling-patches-r214630-old cling-patches-r225983 cling-patches-r226163 cling-patches-r227305...

have seen `r302975` in one of the previous PRs, https://github.com/Homebrew/homebrew-core/pull/47309

ping @SimeonEhrig

yeah, I noticed the tags were missing for llvm (it was built fine with `cling-0.7`, so I did not report that issue :) ).

@SimeonEhrig do mind tagging those two commits in the two repos (I could not do the branch checkout on the homebrew side)

AFAIC it wont have any issues, in fact, I already saw the version mismatch in the test log, but it should not be a big issue, what do you think?

> I'm afraid I do not understand homebrew enough (I don't work with mac). @rotemamsa what do you think? @chenrui333 How do other releases work? Is there always a mismatch...

> you specify "hard coded" version (147) in url path. can you please explain why is that? we see that when we are running "brew install kubescape" we are sill...