chore: remove homebrew publishing

[toddbaert]

Remove homebrew. It hasn't been working for a while and requires constant attention in another repo.

My justifications:

• flagd is a "cloud native" tool - it easily runs in docker, even on darwin/arm (homebrew is really not for cloud infra)
• maintenance burden
• low usage

Feel free to disagree, but if you do, you are committing to fixing it and taking care of it 😁

[netlify]

✅ Deploy Preview for polite-licorice-3db33c ready!

Name	Link
🔨 Latest commit	d6e4190
🔍 Latest deploy log	https://app.netlify.com/projects/polite-licorice-3db33c/deploys/69a85a77a2763400080f0bbb
😎 Deploy Preview	https://deploy-preview-1890--polite-licorice-3db33c.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

The primary goal of this pull request is to streamline the flagd project's distribution channels by discontinuing support for Homebrew publishing. This change aims to reduce maintenance overhead and focus resources on more stable distribution methods, as the Homebrew integration has been non-functional and required constant attention.

Highlights

• Homebrew Publishing Removal: This pull request removes all references and mechanisms for publishing flagd via Homebrew. The decision was made due to persistent maintenance issues and the current non-functional state of the Homebrew integration.

Changelog

• docs/installation.md
  • Removed Homebrew installation instructions.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release-please.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request removes the Homebrew installation instructions from the documentation. The change correctly deletes the relevant section from docs/installation.md, aligning with the stated goal of discontinuing Homebrew support due to maintenance issues. The change is straightforward and no issues were found.

_{Note: Security Review has been skipped due to the limited scope of the PR.}