Skip to content

BidiLens Android 0.1.1

Choose a tag to compare

View all tags
@CodeinScrubs CodeinScrubs released this 28 Jul 08:05
Immutable release. Only release title and notes can be modified.
android-v0.1.1
c59a5b6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

BidiLens Android 0.1.1 is the first signed Android release published to Maven Central.

Maven Central coordinates

dependencies {
    implementation(io.github.codeinscrubs.bidilens:bidilens-core:0.1.1)
    implementation(io.github.codeinscrubs.bidilens:bidilens-android-views:0.1.1)
    implementation(io.github.codeinscrubs.bidilens:bidilens-android-compose:0.1.1)
}

Use mavenCentral() in dependency repositories. bidilens-core and bidilens-android-views support Android API 21+; bidilens-android-compose supports API 23+.

Integrity and provenance

  • Release commit: c59a5b674482081980fc886f6d38036f88af5dc8
  • CI run: 30337482079
  • Maven Central release run: 30339097846
  • Central deployment: 82599fc9-fc43-44ba-8268-f7bd6c68a9a6
  • OpenPGP signing-key fingerprint: B635 C698 5216 FC5D EB5D DCDD 68BE 2D5C E18F 72C6

All 15 primary Central files (AAR, sources JAR, documentation JAR, POM, and Gradle module metadata for each module) were downloaded after publication and matched the retained workflow outputs byte-for-byte. All 15 detached OpenPGP signatures verified, all 30 published MD5/SHA-1 checksums matched, and a clean Gradle consumer with an empty Maven Local resolved all three modules from Maven Central and built successfully.

SHA256SUMS.txt covers every other attached release asset. The Central evidence archive includes the public files, signatures, and Central checksums. The Maven repository archive is suitable for offline inspection or local-repository testing.

Scope and limitations

BidiLens provides conservative direction detection, isolation, Android Views helpers, Jetpack Compose helpers, and editable-text selection preservation. It does not replace Unicode Bidirectional Algorithm rendering or guarantee every OEM keyboard, accessibility service, custom renderer, or physical-device combination without integration testing. Physical OEM/IME/TalkBack validation and external production pilots remain ongoing. The documentation JARs are intentionally minimal compatibility artifacts; source-level API documentation remains in the repository.

Assets 12
Loading