brew install prints a `postflight` deprecation warning
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start with the generated Cask at Casks/markfluence.rb (the warning points to line 39) and trace it back to the GoReleaser source that generates it. Check how the tap and postflight hook are configured there. Done means a fresh brew install markfluence completes without the deprecation warning and points users to a valid place to report issues.
Written by the indexing model from the issue text.
Description
brew install markfluence prints a deprecation warning and tells me to report it to a tap that doesn't exist.
What I did
brew tap mozilla/markfluence https://github.com/mozilla/markfluence
brew trust mozilla/markfluence
brew install markfluence
What I got
Warning: Calling `postflight` is deprecated! Use `postflight_steps` instead.
Please report this issue to the mozilla/homebrew-markfluence tap (not Homebrew/* repositories), or even better, submit a PR to fix it:
/opt/homebrew/Library/Taps/mozilla/homebrew-markfluence/Casks/markfluence.rb:39
Two things about that message are confusing on their own:
- It says to report to
mozilla/homebrew-markfluence, which is a 404. The tap ismozilla/markfluence— the repo is its own tap — andhomebrew-markfluenceis only the directory name Homebrew uses locally. - It points at a file with
# This file was generated by GoReleaser. DO NOT EDIT.at the top, so the suggested PR would be overwritten by the next release.
What I expected
A clean install with no warning.
Does it actually work?
Yes. The install completes, markfluence --version reports markfluence 0.1.0 (1d0a2d0, 2026-09-20), and shell completions work. It's noise, not breakage — but it's noise on the very first thing a new user does, and it reads like something is wrong with the project.
Environment
- macOS 26.6.2 (arm64)
- Homebrew 7.0.4
- markfluence 0.1.0
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 50
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla/markfluence
-
polish the prose Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
mozilla/markfluence#165 ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 48/100
mozilla/markfluence#163 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
mozilla/markfluence#162 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
mozilla/markfluence#157 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
mozilla/markfluence#152 ·
All issues in mozilla/markfluence
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100