-
Notifications
You must be signed in to change notification settings - Fork 208
Deploying a new release
Seth T edited this page May 24, 2022
·
2 revisions
Current steps:
- Increase the version number in Amber to the new target version number. Make sure this includes the
src/amber/version.cr
file, the CLI commandamber -v
provides this version. - Make a new branch, named the version that is being deployed.
- Make a new "Release" tag, using the same version number. Update the release notes with any changes that may affect users.
- Before merging in any new PRs, make a PR to merge the latest updates from master into the
stable
branch for the Linux users
To update Homebrew:
- Download a copy of the new release tar file
- Run
shasum -a 256 /directory/of/file/file-name.tar.gz
to get the SHA for the file. - Update the formula in the Homebrew-amber directory, the file link and SHA values in
Formula/amber.rb
take the link to the new tar.gz file and the SHA value you just calculated in your terminal. - Push the updates in the Homebrew formula to master and run
brew update
.