Deployment

Deploy

Update src/MacVim/Info.plist CFBundleVersion to NUMBER.
Commit src/MacVim/Info.plist with meaningful commit log like this and push it.
Create a signed annotated release-NUMBER tag (make sure you have Git set up to sign, and the signature is registered at Github) and push the tag to the origin (assuming "origin" is the name of the remote to this repository):
```
 $ git tag -a -s release-NUMBER
 $ git push origin release-NUMBER
```
- Don't use git push origin --tags!
Go to the Tags page and find the tag you made and create a release out of it. Choose a title similar to previous releases (e.g. "MacVim Snapshot 155"), and paste in the commit message to the descriptions. Clean up the message and add screenshots / videos as needed to make it look good. Wrap the "Compatibility" section under a <details><summary>Compatibility</summary> ... </details> block so they don't waste space.
GitHub Actions CI will create an artifact under the tag. Download it, sign / notarize the app, and upload the dmg to the release.
Once the release is in a good shape, do git push origin to push the commit to master itself. After doing this you should not change anything in the release anymore. If a regression happens, just push a new release to revert the change.
Update Sparkle's appcast xml file so updater will start pointing to the release.

Refer to http://docs.travis-ci.com/user/deployment/releases/
Update .travis.yml in master branch
- Use travis command if you need to update api_key, but it will reformat the all file, just please update api_key:.

    $ travis setup releases