Always use most recent jbang

[koppor]

Today, I get

Found JBang v.0.116.0

But locally, I have

$ jbang --version
0.126.3

Naive expection: Plugin should use latest JBang version. Maybe with an update check once a day.

[aalmiray]

Hmm not so sure about this one. Perhaps setting the version property of the jbang task to "latest".

If so, then download jbang from https://github.com/jbangdev/jbang/releases/latest/download/jbang.tar, extract it, obtain the version number, and display it.

There must be a way to query the matching version using an http HEAD to avoid downloading the latest .tar all the time.

[koppor]

I currently see https://www.jbang.dev/releases/latest/download/version.txt being downloaded. It is a simple text file containing the string of the latest version

Example

0.126.3

I think, it is OK to just GET this file as the repsonse fits into a single chunk, doesn't it?

[maxandersen]

The default semantics we have everywhere else is that if nothing else specified we use the version found in PATH, if not found then ~/.jbang/bin and if not found then download latest.

if we need something like absolutely latest we should have some other flag for consistency.

[aalmiray]

Right. Which is why using latest as explicit value for the task’s version property would be my recommendation.

[maxandersen]

But why is gradle finding 116 and not 125 as in users path?

[aalmiray]

Because 116 was likely cached first by the jbang gradle plugin and then 125 was installed via jbang.

[koppor]

Using an existing version would also solve the issue, if version.txt cannot be downloaded

Note: "JBang not found." is OKish, but I don't understand - jbang 0.137.0 is installed.

[koppor]

Maybe some issues with the PATH on Windows?

$ which jbang
/c/Users/olive/AppData/Local/UniGetUI/Chocolatey/bin/jbang