A detailed description of the proposed feature

When upgrading a bottle, first download the new version, then remove the old one and, finally, install the new.

The motivation for the feature

When upgrading things, the thing being upgraded will be unavailable for some time, since its first removed and then the download starts.

I regularly run brew upgrade and keep working since it

Apparently it should work now but it's not clear how to get there: github/hub#2149

Can you document it somewhere?

Originally posted by @core-code in Homebrew/homebrew-cask#69611 (comment)

i think i can add something to our current knowhow about finding appcasts for apps ( https://github.com/Homebrew/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/appcast.md )

many electron based apps contain a file in Contents/Resources/app-update.yml

this file

Is your feature request related to a problem? Please describe.
It's not exactly straight forward to install goreleaser and use it in GitLab CI. I wouldn't opt for this - https://goreleaser.com/ci/#gitlab-ci

Describe the solution you'd like
A solution that allows me to use goreleaser in my GitLab Ci with a simple config such as this:

release-job:
  image: some-image
  stage: 

Hi!

As an enhancement it would be nice if you could implement in the future the possibility to play single player on other difficulties than normal, ie nightmare and hell.
There was som weird ways to force the original into nightmare and hell difficulty so this should be possible.
This was how it was done:
https://www.youtube.com/watch?v=0fwXdDBviBQ

Would it be possible to add something in the README about the difference between large heap and non-large heap binaries? I'm a little confused about whether this issue effects anything besides launching Eclipse.

Originally posted by @timgilbert in AdoptOpenJDK/homebrew-openjdk#87 (comment)