Repository navigation
chore: publish to shared homebrew-tap and macports-ports repos - #55
Merged
Merged
Conversation
teknikqa
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publishes releases to the renamed shared distribution repos:
teknikqa/homebrew-tap(washomebrew-upkeep) andteknikqa/macports-ports(wasmacports-upkeep). One tap and one ports tree now serve every app, starting with ai-usage-meter next.What Changed
homebrew-tapmacports-ports; the Portfile pathsysutils/upkeep/Portfilestays the samebrew install teknikqa/tap/upkeepWhy
A separate tap per app doesn't scale. GitHub redirects the old repo names, so existing users keep receiving updates under their old local tap name.
CHANGELOG.mdkeeps the old names because it records past releases.The
HOMEBREW_TAP_GITHUB_TOKENandMACPORTS_TAP_GITHUB_TOKENsecrets need no changes if they are fine-grained tokens scoped to the repos: a rename doesn't change a repo's ID.