| Age | Commit message (Collapse) | Author |
|
Will only happen once but could be confusing anyway.
|
|
info: print requirements
|
|
doctor: remove outdated Homebrew check.
|
|
This is no longer relevant in the bright, new tagged future.
Fixes #1151.
|
|
Only run for Homebrew developers so assume they don’t want to switch
back to an old stable branch.
Fixes #1141.
|
|
This makes the code easier to follow rather than having to know
HOMEBREW_NO_UPDATE_CLEANUP implies not updating to a tag.
|
|
|
|
|
|
Otherwise if we've committed to `master` and someone `brew update`s
before we cut the tag then they won't be updated to the latest version.
|
|
update.sh: always use stable branch for tags.
|
|
This avoids creating a new branch that’ll never be deleted for each tag
and differentiates between the `master` and `stable` branches.
|
|
update.sh: do not restore stable (tag) branch
|
|
|
|
Restoring stable branch post-update could lead to unsuspecting users
with homebrew.devcmdrun being stuck forever on an old tag.
Fixes #1111.
|
|
Store the formula used to build the keg inside the keg in a
file named NAME/VERSION/.brew/NAME.rb after removing the
bottle do ... end block.
See https://github.com/Homebrew/brew-evolution/pull/6.
Closes https://github.com/Homebrew/brew/issues/931.
|
|
|
|
|
|
|
|
|
|
update.sh: only update to semver tags.
|
|
Otherwise random e.g. `pr-123` tags may cause `brew update` to update
to the wrong version.
|
|
If we have a HOMEBREW_REPOSITORY and HOMEBREW_PREFIX mismatch (now the
default) then we can block access to the whole of HOMEBREW_REPOSITORY
rather than just the HOMEBREW_LIBRARY and `.git`.
|
|
It’ll only get printed for people getting updated to tags now and these
are people who haven’t run a `dev-cmd` so we want to air on the side of
telling them less stuff that will confuse them and assume people who
have manually made another `git` branch will know how to get back to it.
|
|
When exactly two versions of a package were installed, the uninstall
message should not read "Remove them all with...", since only one
version remains.
"Remove all versions with..." is flexible enough to avoid being
interpreted as grammatically incorrect, and it still accurately
describes the general behavior of `brew uninstall --force`.
|
|
- Don't let the `UPSTREAM_TAG` variable bleed into future repository
checks.
- Even if the tag branch is an ancestor of the tag ensure that it's
forced back to the tag anyway.
|
|
To test the tag update functionality allow setting
`HOMEBREW_UPDATE_TO_TAG`.
|
|
Rather than following every change on `master` let’s have non-developer
users (i.e. those who have never run a `dev-cmd` or set
`HOMEBREW_DEVELOPER`) update between tags.
This provides a fairly natural beta (the `master` branch`) and stable
(the tags) approach without restricting us to any particular way of
managing our tags.
|
|
|
|
We use these for updating people who just follow tags.
|
|
|
|
|
|
|
|
If we have a `brew.sh` which has set
`HOMEBREW_ENABLE_AUTO_UPDATE_MIGRATION` then let's allow an auto-update
migration. That's because it contains the fix below it _before_ the
update happened which means the auto-update won't fail in the same way
as if updating from an old version.
|
|
|
|
|
|
|
|
|
|
Make `brew upgrade` and `brew outdated` follow alias changes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
References #1023.
|
|
update-report: migrate everyone to new repository.
|
|
Use new "macOS" naming where appropriate.
|
|
|
|
This will hang around otherwise due to e.g. running `bundle install` in
here once.
|
|
Before stashing also try to cancel any current merge, rebase and
reset. This will prevent any data loss but also make the stash more
likely to succeed.
|