Why do m-ab-s compile rav1e v0.6.1 when the latest official rav1e release is v0.6.6?

[Barough]

So, what's going on with this....... Why do m-ab-s compile rav1e v0.6.1 when the latest official rav1e release is v0.6.6?

m-ab-s compile rav1e binary

D:\test\rav1e-mabs.exe --version rav1e 0.6.1 (p20230516-3-g0cbfd71) (release)

Dowloaded from rav1e's Github page https://github.com/xiph/rav1e/releases/tag/v0.6.6

D:\test\rav1e.exe --version rav1e 0.6.6 (v0.6.6) (release)

[LigH-de]

At least the shell scripts don't seem to contain a lock to a specific commit.

ab-suite.git.reset.log reports as last version: b26b1431 Readd logging which was accidentally hidden behind tracing feature which is in sync with the last commit in the repo's web view.

The file Cargo.lock reports:

[[package]]
name = "rav1e"
version = "0.6.1"

[Barough]

I couldn't find reason in the logs etc. but u found something.

Wait and see what @1480c1 have to say

[L4cache]

I think it still has the latest code (as the time you built it) given the commit hash exists in the source repo and was commited at the same date in your version string, so very likely the version was just misconfigured

[1480c1]

From what I see,

https://github.com/xiph/rav1e/blob/master/Cargo.toml#L3 https://github.com/xiph/rav1e/blob/0.6/Cargo.toml#L3

The master branch's version is simply not updated? Not sure why at this time,