pulsarctl 3.3.0.3 (new formula)

[branchvincent]

• 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 HOMEBREW_NO_INSTALL_FROM_API=1 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 HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

Needed a livecheck due to an old calver tag and github_latest isn't accurate either (latest is v3.0.5.4 but their tap is on v3.3.0.1)

[chenrui333]

why not use latest v3.0.5.4 ?

[branchvincent]

Cause

latest is v3.0.5.4 but their tap is on v3.3.0.1

So it seems like they are maintaining multiple minor versions in parallel

[chenrui333]

I feel like it is more of goreleaser flow issue :), can you raise an upstream issue to confirm about this? I'd prefer 3.0.5.4

[branchvincent]

Are they using goreleaser? I don't see a .goreleaser.yaml

But streamnative/pulsarctl#980 (comment) confirms they are maintaining muliple minor versions in parallel, as they track the same minor versions as pulsar (and the latest there is 3.3.x)

[chenrui333]

yeah, they dont use it, it would be better that they use it to automate the tap updates.

[github-actions]

@branchvincent has requested bottles to be published to this PR.

[github-actions]

⚠️ @branchvincent bottle publish failed.

[github-actions]

@branchvincent has requested bottles to be published to this PR.