Open
Description
I'm trying to get SwiftBar updated in Homebrew and ran into 2 issues:
- The method recommended by the contributing guide to update a cask,
brew bump --open-pr swiftbar
, didn't work because it was looking for the release asset with build numberb520
from 2.0.0, while 2.0.1 usesb536
, so I had to create the PR manually. - One of the required verification steps,
brew audit --cask --online swiftbar
, fails for presumably the same reason.
If the build number were removed from the filename, that would make automation tasks like this easier to set up.
Activity
melonamin commentedon Feb 27, 2025
You are saying that having a stable
SwiftBar.zip
will help to address this issue?fenhl commentedon Feb 27, 2025
SwiftBar.v2.0.1.zip
, without theb536
part, should also be fine. The version number is already required to build the full URL after all.melonamin commentedon Feb 27, 2025
Updated in the latest release, so you can give it a try.
I would need to update the Sparkle thingy, but that shouldn't be too much work.
Update swiftbar URL for swiftbar/SwiftBar#433
fenhl commentedon Feb 27, 2025
Thanks, I can't test it anymore because the PR already exists now, but we'll know for sure on the next release after 2.0.1.
mtscope commentedon Mar 2, 2025
Think this may have caused an issue with being able to update or install via homebrew?
https://github.com/swiftbar/SwiftBar/releases/download/v2.0.1/SwiftBar.v2.0.1.zip
vs
https://github.com/swiftbar/SwiftBar/releases/download/v2.0.1/SwiftBar.v2.0.1.b536.zip
fenhl commentedon Mar 2, 2025
Looking at https://github.com/swiftbar/SwiftBar/releases/tag/v2.0.1 it seems like the release asset name was reverted to include the build number again. I had removed it from the Homebrew PR (Homebrew/homebrew-cask#203229) following #433 (comment).
@melonamin Was this intentional? Should we adjust Homebrew to include the build number again?
melonamin commentedon Mar 2, 2025
@fenhl Yeah, I did it yesterday on the go and forgot to comment here; sorry.
Autoupdate relies on this versioning scheme, and there is no easy way to fix it, so we're stuck with it for now.