brew pin

Homebrew's `brew pin` command prevents the LogSeq formula from being upgraded, as demonstrated by a user who pinned LogSeq at version 0.10.14 to avoid the breaking changes in LogSeq v2.0.1. The user, who relies on markdown files and AI-assisted editing, cited community criticism that LogSeq v2's database format undermines its original vision. The pin command, though effective, warns that LogSeq's auto-update feature may bypass the pin.

♠ TIL : brew pin https://docs.brew.sh/FAQ :~:text=brew%20upgrade%20%3Cformula%3E-,How%20do%20I%20stop%20certain%20formulae%20from%20being%20updated%3F,-To%20stop%20something . For reasons to be elaborated in another post, I am currently prevented from upgrading LogSeq https://logseq.com/ to its latest version in homebrew: % brew outdated ... logseq 0.10.14 = 2.0.1 ... LogSeq v2 https://news.ycombinator.com/item?id=48896229 introduces breaking changes to my workflow. I found this out the hard way. As put by Valodim in HN: And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files? At a time when half the edits are done by Claude and tracked with jujustu, this is just not useful for me. All I wanted was the original vision, but with less bugs and more quality of life features. As such, I would like to settle in the current version for now. Pinning to the rescue % brew pin logseq Warning: logseq has auto updates true and may update itself outside Homebrew despite being pinned. % brew list --pinned logseq % brew outdated ... logseq 0.10.14 = 2.0.1 pinned at 0.10.14 ... That’s all. To unpin it in the future: % brew unpin logseq — § — Reply via email mailto:serendipity@perrotta.dev?subject=Reply to: brew pin