Full apk support is very nearly complete. Details above.
All of the code changes are merged, all upstream services have incorporated the changes (most notably ASU server), but the changes have yet to propagate through the builds for all devices. Here's how you can tell if your device is ready.
First, rpcd version 2025.06.22 or later must be available on your device.
$ apk update && apk list rpcd
rpcd-2024.12.02~cc9a471c-r1 ... bad! old pre-abiversion
rpcd-2025.06.22~9389775c-r1 ... good! new contains abiversion handling
If you only see the 2024.12.02 version, you'll have to wait.
Second, the available imagebuilder must be at r30201 or later. As I'm writing this, most of them are new enough, but check first (I'm seeing 30208 on most of my builds today).
$ owut check
...
Version-to SNAPSHOT r30208-1ce0eb5bf2 (kernel 6.12.34)
...
When both of these conditions are met you can upgrade one last time with the hackity hack hack mchackface:
missing=$(owut check -v | awk '/missing to-version/ {print $1}')
echo $missing
# Make sure the missing list looks right!
# Should be just 'lib*' entries...
owut upgrade -r "$missing"
Then we wait for the next ABI-versioned package to be built and see if it all works!