···53535454If you want to publish to Homebrew, you can create your own "tap" repository with a "cask" file for this script. You may want to Google how all that works. For reference, my tap can be found [here](http://github.com/probablykasper/homebrew-tap).
55555656-1. Create a tarball of your repo by running the following:
5757- ```
5858- git archive HEAD -o dist/to-VERSION.tar.gz
5959- ```
6060-2. Create a GitHub release with the release notes and attach the tarball
6161-3. Your cask file needs a url pointing to the tarball.
6262-6363- The url should be in this format: `https://github.com/USER/REPO/raw/master/dist/to-VERSION.tar.gz`
6464-4. After putting a url in your cask file, you need a sha256 string. Homebrew will geenrate it for you when you run this inside your tap repo:
5656+1. Update `CHANGELOG.md`
5757+2. Create a git tag + GitHub release with the release notes
5858+3. Update the cask's `url` to be the archive of the latest tag. This URL will be in this format: `https://github.com/USER/REPO/archive/refs/tags/VERSION.tar.gz`
5959+4. Update the `sha256`. Once you have the url updated, you can let Homebrew generate it for you by running this inside your tap repo:
6560 ```
6666- brew cask fetch ./Casks/to.rb
6161+ brew fetch --cask ./Casks/to.rb
6762 ```
6868-5. Update `CHANGELOG.md`