Skip to content

tinybus-module-release.md

Latest commit

 

History

History
45 lines (39 loc) · 2.37 KB

tinybus-module-release.md

File metadata and controls

45 lines (39 loc) · 2.37 KB
Raw

TinyBus Module Release

Purpose

Generated projects must be usable as native TinyBus integrations and distributable without also shipping the TinyBus host runtime.

Contract

  • The library builds as both an rlib and a native cdylib.
  • The cdylib exports TinyBus module ABI v1, an embedded manifest, and the initialization entrypoint.
  • The module provides the fifty-nine members of ai.tinyhumans.tinycomputer.Desktop at /ai/tinyhumans/tinycomputer/Desktop.
  • Each release archive is named tinycomputer-<version>-<platform>.<extension> and contains only this module, its SHA-256 modules.toml, license, and installation documentation — plus, on macOS, the engine's agent-desktop-macos-helper, which the engine's clipboard only trusts beside the loaded module.
  • Each GitHub release publishes a separate checksum.toml mapping every archive filename to its SHA-256 digest under a [sha256] table for TinyBus's release loader.
  • Release builds cover the stable native Ubuntu, macOS, and Windows runners, Fedora 43/44 containers, and rolling Arch Linux where official runners or images exist for the architecture.
  • TinyBus itself remains a pinned SDK submodule and is not shipped as a release asset from this repository.

Verification

CI exercises the bus interface through TinyBus's in-memory transport, enforces 90% line coverage in every source file, and builds the cdylib. Maintainers update the root workspace package version and lockfile in a reviewed pull request, then push a vX.Y.Z tag at the merged commit. Release also accepts an existing tag through its required tag dispatch input. The shared release workflow verifies that the tagged commit is on main and that the module's Cargo version matches the tag; it never commits or pushes version updates. It builds each native module from the tagged source, recording its exact digest in the adjacent allowlist. After publishing, it downloads the Ubuntu x86_64 archive through TinyBus's GitHub release API and calls Version over an in-memory bus. Version is chosen because it needs no granted permission and touches no other application, so the gate tests the artifact rather than the runner's configuration. Before loading the archived module, the workflow installs its Linux runtime libraries and checks that ldd resolves every dependency, so a missing host package cannot masquerade as a broken module.