Does tested_libversions need updating?

[MrNaif2018]

Hi! I'm trying to launch electrum from source on macos, and it can't find libsecp256k1
When I do brew install secp256k1, it installs the recent libsecp256k1 0.6.0 released two weeks ago: https://github.com/bitcoin-core/secp256k1/releases/tag/v0.6.0
So inside the folder, I see libsecp256k1.5.dylib
But tested versions are up to 2 only.
See

electrum-ecc/src/electrum_ecc/ecc_fast.py

Line 48 in b2cde56

tested_libversions = [2, 1, 0, ] # try latest version first

When on ubuntu, I usually just run
sudo apt install libsecp256k1-dev
And because of ubuntu slow rollover of packages I guess, the max version I would get is the number 2
Can this list be updated? Is it like, to prevent breaking ABI changes? Or any blocker in recent libsecp which prevents it from using?
Because when I manually added tested versions it does start at least (:

Hmm but also, I tried compiling the 0.5.1 version, and it has ABI version of 2. So I'm not sure, maybe it's their bug that they jumped 3 versions at once?

EDIT: just tested on linux, and it's also a jump of 3 versions there

[SomberNight]

They only bump the ABI version when they make an incompatible change to it. So 0.3.x, 0.4.x, and 0.5.x all used version 2. Now there was a change in 0.6.0, so the ABI version got bumped to 5.
See the changelog re "ABI Compatibility".

The versions themselves are calculated in a somewhat weird way, see bitcoin-core/secp256k1#1055 (comment)