aws-vault 7.3.7

[mbevc1]

Change to maintained fork and bump version

• 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 HOMEBREW_NO_INSTALL_FROM_API=1 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 HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[daeho-ro]

I think you should submit as a new formula, not changing previous one. It is not an official descendant.

[mbevc1]

Project seems abandoned and no response from maintainers for a while. It's a in-place replacement and direct fork. Could we at least retire this and add new one? Otherwise the naming might be overlapping.

[daeho-ro]

Here is our policy to accept forks.

• https://docs.brew.sh/Acceptable-Formulae#not-a-fork-usually

[daeho-ro]

You could add your own tap to use the same formula name, then the full name of the formula will be

brew install your-org/your-tap/aws-vault

• https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

[mbevc1]

Thanks for the suggestion, but I'm not sure I want to maintain my own tap ATM 🤔

[mbevc1]

What'd be suggestion in case project is dead and we cannot get updates upstream anymore?

[mbevc1]

In case we can get a response from anyone at upstream (if maintainers will respond) I've opened: 99designs/aws-vault#1270

[chenrui333]

lgtm

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.

[chenrui333]

Thanks @mbevc1!