Cask 'sbarex-qlmarkdown' is unavailable

[piersolenski]

Long time lover of this plugin.

I recently started running my dotfiles through a GitHub action and I get the following error that makes the CI fail:

Installing sbarex-qlmarkdown
Error: Cask 'sbarex-qlmarkdown' is unavailable: No Cask with this name exists.
Installing sbarex-qlmarkdown has failed!

All other brews and casks install fine except this one. Locally works fine as expected. The GitHub action is set to use macos-latest.

Any idea what might be going on here?

[sbarex]

If I remember correctly, the package was simply renamed to qlmarkdown as the other of the same name is no longer developed (it has been renamed to toland-qlmarkdown)

[piersolenski]

Hmm, qlmarkdown is the one in my Brewfile, but I'm still getting this error. Any idea why it would be trying to install sbarex-qlmarkdown when just using "cask "qlmarkdown"?

[refactorized]

I just today installed this fresh using the documented command:

brew install --cask qlmarkdown

And it seemed to work without a hitch.

Brew updated right before executing (as I think it always does on install). After finding the app, arguing with my system about 'safe' software, and finally running the app, I now have document thumbnails and quick-view capability for .md files.

so that's datapoint for working brew installations.

---

I wonder if brew is updating properly on your system. You may want to run brew update manually to see what it says, and follow any instructions that might pop up about fixing shallow clones.

Failing that you might want to try brew doctor or a fresh install of homebrew.

--
update: Ahh sorry, missed the detail about this only happening in CI, and the shallow clone stuff doesn't happen anymore with new brew installations. Wish I could be more help.

[piersolenski]

It actually installs fine on my system, the issue is happening in the GitHub action, which is a clean install on the latest version of macOS 🤔

[piersolenski]

I understand this might be a bit too niche to deserve its own issue as most people aren't installing the cask this way! I was more curious as to why it was happening and if there was a quick fix, as the whole GitHub action fails if one cask doesn't install.