[mesheryctl] deprecate meshery/homebrew-tap for publishing mesheryctl releases

[nishantwrp]

See mesheryctl Command Tracker for current status of commands.

Description

We've recently added mesheryctl to homebrew-core meaning that we no longer need to push releases to https://github.com/meshery/homebrew-tap. But we're still leaving the systems to publish mesheryctl while we make sure that the release process with homebrew-core is smooth.

Here's what we'd need to do

• Remove brew config from goreleaser.

  meshery/.goreleaser.yml

  Line 60 in a37d97c

  brews:

• Add a tap_migrations.json to ensure that the existing users don't face any issues while updating mesheryctl. (Ref - https://stackoverflow.com/questions/70079331/best-way-to-deprecate-a-homebrew-tap-to-transition-to-another-tap/70089144#70089144)

Environment

• Host OS: Mac Linux Windows
• Meshery Server Version: stable-v
• Meshery Client Version: stable-v
• Platform: Docker Kubernetes

---

Contributor Resources

• mesheryctl Contributing Guide
• Beginner's guide to contributing to Meshery and mesheryctl
• mesheryctl Command Tracker
• Meshery CLI Commands and Documentation
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[github-actions]

This issue has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the mesheryctl command tracker spreadsheet.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.