ruby-completion* 1.0.0

[chenrui333]

• 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>?

---

• also raised an upstream issue about tagging, tag the release? mernen/completion-ruby#15

[chenrui333]

• similar version scheme issue with rdiff-backup: revert from 2.4.0 to 2.2.6 #156900
• also FormulaAuditor: Separate stable version audit brew#16335

[MikeMcQuaid]

• similar version scheme issue with rdiff-backup: revert from 2.4.0 to 2.2.6 #156900

This is not the same because it's an actual downgrade.

In a case like this PR: using version_scheme is legitimate because it is an actual upgrade with an actual version scheme change.

[chenrui333]

aha, I will use the version_scheme, thanks @MikeMcQuaid! 👍

[github-actions]

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