Closed rolandwalker closed 3 years ago
I don't know Cask very well, but apparently it is installing
tree-sitter-langs
v0.10.6-alpha because that's the latest tag (and there's no way to pin Cask to an earlier version). Then it's attempting to install v0.10.6-alpha artifacts which don't exist.
I entirely forgot about melpa-stable
... The above tag will have binaries as soon as I fix the release pipeline. I'll also change the MELPA recipe to restrict it to a subset of tags.
The Caskfile is using
melpa-stable
as the source.
I think melpa-stable
is discouraged in general. There's even a proposal to abolish it. Maybe it's better to change the Caskfile to use melpa
? (In my own experience, melpa-stable
got broken more frequently than melpa
when I was still using it.)
Is there a way to override the version attempted for the grammar bundle install? If not, would you accept a PR to add an override via
getenv
?
There's no way to override that at the moment. I think changing tree-sitter-langs--bundle-version
to a defvar
is cleaner than getenv
. However, it wouldn't help in this case, since cask
doesn't have pre-install hooks.
The release pipeline is working now, so the pygn CI pipeline should work if you re-run it.
Thank you!
Pygn-mode CI:
Is failing like this:
I don't know Cask very well, but apparently it is installing
tree-sitter-langs
v0.10.6-alpha because that's the latest tag (and there's no way to pin Cask to an earlier version). Then it's attempting to install v0.10.6-alpha artifacts which don't exist. The Caskfile is usingmelpa-stable
as the source.Is there a way to override the version attempted for the grammar bundle install? If not, would you accept a PR to add an override via
getenv
?