Install mcpc with Homebrew via apify/homebrew-tap - #357
Merged
Conversation
Let macOS and Linux users install mcpc with "brew install apify/tap/mcpc" instead of setting up Node.js or Bun first. The formula lives in apify/homebrew-tap next to apify-cli, and a full release now dispatches that repository's existing update_formula.yaml workflow, which points Formula/mcpc.rb at the new npm tarball, installs and "brew test"s it on Linux and macOS, then merges the bump. A failed dispatch only warns, since the release is already published by then. Refs #355 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BcRjUSnuwKjKhQRgKQ1zzv
jancurn
changed the title
jancurn
changed the title
Move the tap dispatch to the very last step of the release job and mark it continue-on-error. It previously sat between the npm publish and the GitHub release creation, so a hard failure there (no `gh` on the runner, a missing token, the tap workflow renamed) would have skipped the release-page step for a version that was already tagged and published. The dispatch now runs only after the version is tagged, published to npm and has a GitHub release, and it cannot fail the job. Homebrew users keep the previous version until the bump is re-run from the tap's Actions tab; npm and Bun users are unaffected either way. Refs #355 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BcRjUSnuwKjKhQRgKQ1zzv
jancurn
changed the title
Start the formula bump in apify/homebrew-tap by hand for now: the release workflow only prints the `gh workflow run` command in its run summary instead of dispatching it. Skipping the bump leaves Homebrew users on the previous version; npm and Bun installs are unaffected. The step stays last and continue-on-error, and the comment records how to automate it later. Refs #355 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BcRjUSnuwKjKhQRgKQ1zzv
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
3 participants
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.
Lets macOS and Linux users install mcpc with
brew install apify/tap/mcpcinstead of setting up Node.js or Bun first. The formula lives in apify/homebrew-tap next toapify-cli(added in apify/homebrew-tap#55).Its bump is started manually for now — the release workflow only prints the
gh workflow runcommand in its run summary rather than dispatching it. That workflow pointsFormula/mcpc.rbat the new npm tarball, installs andbrew tests it on Linux and macOS, then merges the bump.CLAUDE.mdcontinue-on-error, so nothing Homebrew-related can fail a release that is already tagged, published to npm and announcedMerge apify/homebrew-tap#55 before the first bump, otherwise there is no formula to update.
Fixes #355
🤖 Generated with Claude Code
https://claude.ai/code/session_01BcRjUSnuwKjKhQRgKQ1zzv