pipe-rename 1.4.2 (new formula)

[PythonCoderAS]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• 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?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

I had to use --version as the test because for normal usage a tty is required.

[carlocab]

Please use the preferred commit-message style for homebrew/core. We put the name of the formula first in commit-message headings.

For new formulae:

At Homebrew, we like to put the name of the formula up front like so: foobar 7.3 (new formula).

For existing formulae:

The preferred commit message format for simple version updates is foobar 7.3 and for fixes is foobar: fix flibble matrix..

Refer to the commit style guide for more details. Also, when making further changes to your pull request, use the following guidelines to make sure that @BrewTestBot can merge your commits:

• One formula per commit; one commit per formula.
• Keep merge commits out of the pull request.

[carlocab]

Can we use a GitHub tarball?

[PythonCoderAS]

There are no github releases and the last github tag is version 1.1.6 from September 2020.

[chenrui333]

LGTM

[BrewTestBot]

@chenrui333 has triggered a merge.

[chenrui333]

@PythonCoderAS, thanks for your contribution to Homebrew! 🎉 🥇

Without awesome contributors like you, it would be impossible to maintain Homebrew to the high level of quality users have come to expect. Thank you!!!!