Releases

tubebrain publishes versioned GitHub Releases from tags on main.

Start here if you want to understand:

  • what a release contains
  • where release assets live
  • how to read release notes and the changelog

For installation commands, use Install.

Release Surface

Each tagged release currently publishes:

  • tubebrain-aarch64-apple-darwin.tar.gz
  • tubebrain-aarch64-unknown-linux-gnu.tar.gz
  • tubebrain-x86_64-unknown-linux-gnu.tar.gz
  • SHA256SUMS
  • install.sh
  • tubebrain.rb
  • tubebrain-npm-package.tgz

The latest published release is always available from:

The latest release assets are also mirrored publicly for anonymous installs:

Release Notes And Changelog

tubebrain uses GitHub's autogenerated release notes for the release body and keeps a repository changelog for the higher-level history:

  • GitHub releases: per-tag assets, autogenerated notes, and download links
  • CHANGELOG.md: canonical in-repo release history

Release notes are shaped by .github/release.yml, which groups merged pull requests into feature, fix, docs, packaging, and catch-all sections when labels exist.

Current Line

As of May 15, 2026, the current shipped line is v0.1.10.

Highlights in the current line:

  • first TubeBrain-named release assets after the yt-text rename
  • three published binary targets
  • checksum publishing
  • curl-to-shell installer, Homebrew formula, and npm wrapper
  • po-token compiled into release binaries so default installs work against current YouTube BotGuard traffic
  • authenticated private-repo install support in the installer and npm wrapper
  • public Pages mirroring of the latest release assets for anonymous installs
  • serialized honey Linux release jobs (gnu targets, was musl in v0.1.8) with CARGO_BUILD_JOBS=1 to avoid release runner OOM and upload instability
  • npm registry publication as tubebrain@beta on npmjs.com with SLSA provenance, and a GitHub Packages mirror as @jesssullivan/tubebrain
  • version parity enforcement across workspace manifests and the npm wrapper via scripts/check_release_metadata.py
  • public docs site with install, integrations, quickstarts, troubleshooting, and roadmap coverage

Release Expectations

Every release should keep these surfaces aligned:

  • workspace version strings
  • GitHub release assets
  • Pages mirror assets
  • install docs
  • agent/client docs when configuration behavior changes
  • CHANGELOG.md

If a release changes install paths or packaging posture, the install page is the canonical place to document it.

Runner Authority Policy

tubebrain treats the runner boundary as an explicit product contract:

  • authoritative CI, docs build, Linux release builds, release publication, and npm publishing run on self-hosted Tinyland lanes
  • the Apple Silicon macOS artifact is built on the self-hosted tinyland-darwin lane
  • GitHub-hosted runners remain only for bounded exceptions outside that core authority path: actions/deploy-pages still uses the hosted OIDC route
  • nightly cargo-fuzz runs on the self-hosted tinyland-nix lane and enters the Nix dev shell before installing or running the fuzzer

So the repo should be read as self-hosted by authority, with a small number of durable hosted exceptions by policy.

Known Limits

  • GitHub-hosted anonymous installs still depend on repository visibility, so the public Pages mirror is the recommended anonymous path while the repo is private
  • the nixpkgs package is not published today
  • GitHub Releases and the public Pages mirror are the primary distribution surfaces today, not crates.io