To release Brisk there are a few steps you need to take:
- Update the Version and Build in the
Info.plistto the version from the new release - Change the
mastersection in theCHANGELOG.mdto match the new release version. Don't add a new section for master changes yet - Commit both those changes on master with the message
Bump version $VERSION - Tag the new commit with the version number of the release. Push the commit and the tag
- Archive Brisk in Xcode
- Create a
tar.gzfrom the archivedBrisk.appwithtar -pvczf Brisk.app.tar.gz Brisk.app - Copy the output of
shasum -a 256 Brisk.app Brisk.app.tar.gzfor later - Draft a release on GitHub with the newly pushed tag
- Title the release based on whatever feature / bugfix is "most important"
- Fill the description with the contents of the changelog (you might need to join lines in the markdown to get it to render on a single line)
- At the bottom of the description include the output of
shasumfrom the previous step in triple backticks - Upload
Brisk.app.tar.gzto the release - Save / create the release
- In the
appcast.xml, duplicate the top item, and paste it above - Change the title, enclosure url,
sparkle:version,releaseNotesLinkurl to the new version - Get the size of the new
Brisk.app.tar.gzwithstat --printf="%s" Brisk.app.tar.gz. Replacelengthwith that - Sign the release with
path/to/sparkle/sign_update Brisk.app.tar.gz path/to/dsa_priv.pem. Replace thesparkle:dsaSignaturewith that - Update the
pubDatewith the output ofdate +"%a, %d %b %G %H:%M:%S %z" - Commit the appcast changes with the message
Update appcast for $VERSION. Push the commit (note GitHub takes some time to propagate these changes) - Add a new
mastersection in theCHANGELOG.mdfor future changes and commit it - Submit a PR to update the Brisk formula in homebrew-cask
- Celebrate!