Homebrew

WAIL is distributed as a homebrew cask. Updates should follow a procedure after releasing a .dmg to GitHub.

Edit:

cask "wail" do
  version "0.2025.03.03"
  sha256 "db042c83e8617f9e288207fe12f10ccc8af31ac70e07d1d01953c0b95a5ca835"

  url "https://github.com/machawk1/wail/releases/download/v#{version}/WAIL_v#{version}_macOS.dmg"
  name "WAIL"
  desc "Web Archiving Integration Layer: One-Click User Instigated Preservation"
  homepage "https://github.com/machawk1/wail"

  app "WAIL.app"

  zap trash: [
    "~/Library/Application Support/WAIL",
    "~/Library/Preferences/com.matkelly.wail.plist",
    "~/Library/Preferences/WAIL_cli.plist",
    "~/Library/Saved Application State/com.matkelly.wail.savedState",
  ]
end

to correspond with the latest version number as well as calculated the sha256 value with shasum --algorithm 256, targeting the DMG.

Fork https://github.com/Homebrew/homebrew-cask, modifying (repo)/Casks/wail.rb in your local working directory.

Check conformance/compliance with:

• brew cask audit wail --download and
• cd "$(brew --repository)"/Library/Taps/Homebrew/homebrew-cask; brew cask style Casks/wail.rb [--fix].

Add a tightly style commit description (see here), commit, and submit a PR.

Reset local homebrew repo to use latest: cd "$(brew --repository)"/Library/Taps/Homebrew/homebrew-cask; git checkout master

We really ought to separate out the versions via separate hashes. See this other cask's RB for an example and #592 for a justification.