0.2.2 @ 2026/09/15

Bun Runtime 0.2.2.

Requires Android 13 (API 33) or later and AutoJs6 build 5278 or later. Bundles the unmodified official Bun 1.4.0 runtime for arm64-v8a and baseline x86_64 plus a small read-only supervisor helper per ABI; Android API 28-32 remains unsupported.
Run one JavaScript or TypeScript source snapshot with the standalone "bun"; directive. Execution uses bun run --no-install; AutoJs6 globals and a Java bridge are not available. stdout/stderr use bounded Binder callback chunks. Timeouts, cancellation and output limits terminate the Bun child through the supervisor, and runtime error summaries are localized in ten languages.
Multi-file projects: the shared contract now accepts a bounded ZIP workspace archive (workspaceArchiveVersion, workspaceEntryPoint, capability SUPPORTS_WORKSPACE_ARCHIVE) and the plugin expands it into the private per-run workspace so relative imports resolve. The AutoJs6 side that packs a project.json/package.json directory is not part of a released AutoJs6 yet, so released hosts still send single files.
All APKs pass 16 KB ZIP alignment and every ELF payload meets at least 16 KB PT_LOAD alignment. Native arm64 16 KB execution passed the Binder suite on a Samsung SM-A566B (Android 16) with a development build of this plugin; signed-APK acceptance on 16 KB hardware was not repeated for this Release. The official native x86_64 runtime is still rejected on pages larger than 4 KiB.

The three signed APKs and their complete corresponding-source asset set are published separately in this same Release.
Verify every asset with autojs6-plugin-bun-runtime-v0.2.2-SHA256SUMS.txt; the machine-readable source/APK binding is in the corresponding-source manifest.
Bun is MIT-licensed; the executable statically links JavaScriptCore/WebKit components covered by LGPL-2-family terms and contains other third-party components under their respective licenses.
License disclosures and relinking information are in autojs6-plugin-bun-runtime-v0.2.2-corresponding-source-LICENSES-AND-RELINKING.md and in the project-source asset.

The repository's release verifier performed automated technical checks over APK-contained runtime hashes, source closure, archive identities, and GitHub's returned SHA-256 asset digests. This statement records technical verification and does not claim a legal opinion or approval.