This run uses the independent production publishing/ AAR, not the regression
library’s AAR. It was run before the release tag, on merged master cf96da0813d7f9e67d4951d552611cd6ad981ae5
plus the version/publishing/consumer-rule/manifest changes shipped with this entry.
Local build environment: Gradle 7.5, Corretto JDK 11, compile SDK 28 / build-tools 30.0.3.
The hosted publication job and JitPack use JDK 17 with the same Gradle version.
publishToMavenLocal: passed. publication-local.json
records the actual AAR size/hash and each native library’s size/hash.tools:replace.-PstvAar=.../SuperTextView-v3.2.7.aar, with source JNI and source jniLibs excluded.google_apis_ps16k:
47 passed, 0 failed. Both app sysconf=16384 and smaps KernelPageSize=16 kB
are present in the raw run. This is a real 16 KB-kernel virtual
device, not a physical OEM phone. Only ARM64 was loaded in this run.A commit-only JitPack preflight found that its legacy image runs Python 3.5:
ZipFile and ElementTree.parse there reject Path objects. Publication file
paths now cross those APIs as strings, with a regression test that reproduced
this failure before the fix. JitPack’s old standalone sdkmanager also lacks
JDK-17-compatible JAXB classes; AGP successfully installs the required SDK/build
tools using that image’s accepted licenses, so the redundant old manager call
is removed. No Java code or native payload changed in this compatibility fix.
The earlier 470 native executions and 15 UI tests remain separate historical runs. This acceptance does not add physical-device, API 31, GPU/FPS, full GIF conformance, fuzzing, leak or thread-safety coverage. It also does not prove the availability of an externally hosted Maven artifact.
The GitHub Release workflow builds and checks its own production AAR, compiles a
consumer, then uploads the Maven files and SHA256SUMS. Its ZIP/container hash
may differ from the local record due to archive metadata/compiler differences;
the four shipped native byte hashes must remain identical.