Skip to content

Releases: d4rken-org/porter-api

Porter SDK 0.9.0

Choose a tag to compare

@d4rken d4rken released this 30 Sep 21:34

Adds Porter.state, which also reports a running Porter or Shizuku service this SDK can't talk to, so an app can say which side needs an update instead of waiting for a connection that never comes.

implementation("com.github.d4rken-org.porter-api:sdk:0.9.0")

Needs Porter v0.7.0-rc0 or newer (protocol 4).

Integration guide · API reference

Porter SDK 0.8.0

Choose a tag to compare

@d4rken d4rken released this 28 Sep 04:05

Adds shizuku-bridge, which runs code written against Shizuku-API (dev.rikka.shizuku:api) on Porter unchanged, and fixes calls that could hang on the main thread.

implementation("com.github.d4rken-org.porter-api:sdk:0.8.0")

Needs Porter v0.7.0-rc0 or newer (protocol 4).

Integration guide · Shizuku-API bridge

Porter SDK 0.7.0

Choose a tag to compare

@d4rken d4rken released this 24 Sep 16:34

Kotlin-first rewrite of the Porter client SDK. Not source-compatible with 0.1.0, and the client artifact is gone.

implementation("com.github.d4rken-org.porter-api:sdk:0.7.0")

Resolve it from https://jitpack.io. Add sdk-extras for shell commands and system service wrapping.

Needs Porter v0.7.0-rc0 or newer (protocol 4). Apps built on 0.1.0 don't detect this Porter and fall back to their Shizuku path.

Integration guide

Porter SDK 0.1.0

Porter SDK 0.1.0 Pre-release
Pre-release

Choose a tag to compare

@d4rken d4rken released this 07 Sep 18:56

Initial Porter client SDK, preserving compatible Shizuku APIs and adding direct Porter support.

implementation("com.github.d4rken-org.porter-api:client:0.1.0")

Resolve this dependency from https://jitpack.io. It includes the API and provider modules; remove existing dev.rikka.shizuku dependencies and copied Porter adapter classes.

Integration guide