bats-core 0.4.0 (new formula)

[btamayo]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

bats-core is the revival and the happy, growing continuation of the original bats. As there are a good number of bats users and there's been momentum on users migrating to bats-core, we thought it would be prudent to update package manager formulae and release long-anticipated updates as soon as possible.

Side note: There are currently no naming conflicts with this formula and the pre-existing bats formula. But, if the maintainers could give me some advice on how one would "replace" an existing formula that's been seemingly abandoned ~3 years or so, I would be thankful. I'm not sure how common this situation is, and if there are already guidelines on it. Thanks!

[woodruffw]

First of all, thanks for the PR!

Based on the README, this release isn't considered stable yet:

1. Roadmap 1.0: There are already existing high-quality PRs, and often-requested features and issues, especially here at dockward 0.0.3 (new formula) #196. Leverage these and consolidate into a single roadmap.
2. Create or choose a fork or mirror of this repo to use as the new mainline: Repoint existing PRs (whichever ones are possible) to the new mainline, get that repo to a stable 1.0. IMO we should create an organization and grant 2-3 people admin and write access.

Per our formulae guidelines, we can't accept new formulae without a stable version.

I'll leave some review notes above for when this does get to a stable release. Sorry, and thanks again!

[woodruffw]

You can drop this line -- we prefer to build bottles of shell-only packages.

[woodruffw]

(Or maybe not...I see that we allowed for :unneeded in the original bats.)

[woodruffw]

We don't usually like long caveats blobs like this. If bats and bats-core can't play nice when installed at the same time, a conflicts_with statement would be a little cleaner and catch potential mistakes earlier.

[woodruffw]

As an example:

conflicts_with "bats", :because => "both install a `bats` binary"

[btamayo]

@woodruffw Fantastic I really appreciate those tips, thanks! (FWIW There's no new code, this formula simply changes the download origin of the package to the new repo), but I'll definitely update the formula and incorporate this feedback for our stable release! :)

[woodruffw]

Awesome!

FWIW, I'm 👍 on removing bats and aliasing bats-core to it when this is considered stable -- see #20094 as an example of this.

[btamayo]

@woodruffw Thank you! That'll be a huge help :D

[ilovezfs]

Superseded by #28977