Adetailer hard-locked to pretty old version?

[anothertal3]

I intend to switch to the new workflow (control, detailer,...) as described in #3513 while using the API access.

This will take some time, though. Until then I would like to keep using my existing scripts in combination with the "original" backend.

While testing my API access against the current SD.Next version I was baffled to find that adetailer is now hard-locked to a pretty old version ("Mon May20 2024 13:37"):

My current code is targeting at least adetailer a7d96113 ("Sun Jun16 2024 02:32"). It has been working without issues (to my knowledge) for months using an older SD.Next instance (2024-06-24).

Unfortunately, the API seems to has changed between this adetailer version and the older one (e.g., due to typos like ad_tap_enable).

I really don't want to adjust my parameters for an outdated and incorrect API. Is there any reason why this specific version has been locked in place? Or rather: is there a way to override this behavior?

Thanks!

[vladmandic]

Is there any reason why this specific version has been locked in place

i've locked down adetailer since new versions had a tendency to break very often and i dont have time to test every single commit.
btw, if you find a newer commit of adetailer that is confirmed as working, i'll make that one a preferred version.

is there a way to override this behavior?

i've just added override (in dev branch), so if you use --experimental command line flag, it will not reset extension to specific commit, but allow you to use whichever one you choose.

[anothertal3]

Great news, thank you.

I will test around a little bit and try to confirm whether/which newer versions are still functional and report back as soon as the "experimental" gets released.

[vladmandic]

experimental is on dev branch, i don't see the need to merge to master right now - you can use dev branch as-is.