feat: disable spacectl formula in favour of cask#2
Open
alexjurkiewicz wants to merge 1 commit intospacelift-io:mainfrom
Open
feat: disable spacectl formula in favour of cask#2alexjurkiewicz wants to merge 1 commit intospacelift-io:mainfrom
alexjurkiewicz wants to merge 1 commit intospacelift-io:mainfrom
Conversation
The spacectl formula was silently deleted in March 2026 when GoReleaser switched to publishing a cask. Re-add it with disable! so users who have the formula installed get a clear error pointing them to the cask. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Problem
The
spacectlformula was silently deleted in March 2026 when GoReleaser switched to publishing a Homebrew cask instead. Users who had the formula installed (like me!) were left stranded — no upgrade path, no indication of what happened, just stuck on 1.17.0 while the cask moved on to 1.21.1.Fix
Migration for existing users