Skip to content

Releases

BOZKURT CODE v1.0.1

Choose a tag to compare

@github-actions github-actions released this 10 Oct 20:58

BOZKURT CODE v1.0.1

A packaging release on top of 1.0.0: signed in-app updates for the desktop app and release-signed Android builds. No changes to the bz CLI, HTTP API v1, MCP tools or configuration keys.

🌐 Website: https://cumabozkurt.github.io/bozkurt-code/

Downloads

Platform Desktop app CLI (bz, bozkurtd, bozkurt-mcp)
macOS (Apple Silicon) BOZKURT.CODE_1.0.1_aarch64.dmg bozkurt-cli-aarch64-apple-darwin.tar.gz
macOS (Intel) BOZKURT.CODE_1.0.1_x64.dmg bozkurt-cli-x86_64-apple-darwin.tar.gz
Windows x64 BOZKURT.CODE_1.0.1_x64-setup.exe / BOZKURT.CODE_1.0.1_x64_en-US.msi bozkurt-cli-x86_64-pc-windows-msvc.zip
Linux x64 BOZKURT.CODE_1.0.1_amd64.AppImage / .deb / .rpm bozkurt-cli-x86_64-unknown-linux-gnu.tar.gz
Linux arm64 BOZKURT.CODE_1.0.1_aarch64.AppImage / .deb / .rpm bozkurt-cli-aarch64-unknown-linux-gnu.tar.gz

Mobile companion (LAN remote control):

File What it is
bozkurt-mobile-v1.0.1-app-universal-release.apk Android — install this one. Signed with the project release key; later versions install over it.
bozkurt-mobile-v1.0.1-app-universal-release.aab Android App Bundle, signed with the same key (upload key for Play Console)
bozkurt-mobile-v1.0.1-simulator.zip iOS simulator build (Apple Silicon Mac + Xcode); a device/App Store build needs an Apple Developer account

Upgrading the Android app from 1.0.0: the 1.0.0 …-sideload.apk used a throwaway key, so uninstall it once before installing 1.0.1. From 1.0.1 on, updates install in place.

Updater files: latest.json plus a minisign .sig next to every updatable bundle (*.app.tar.gz for macOS, -setup.exe/.msi for Windows, .AppImage/.deb/.rpm for Linux). The desktop app checks releases/latest/download/latest.json on launch, asks before installing, and refuses any update not signed with the project key (D8709082BCE6464D). 1.0.0 had no updater configured, so download 1.0.1 manually once; later releases update in-app.

CLI quick install (verifies SHA256SUMS, no root needed):

curl -fsSL https://raw.githubusercontent.com/cumabozkurt/bozkurt-code/v1.0.1/scripts/install.sh | sh
irm https://raw.githubusercontent.com/cumabozkurt/bozkurt-code/v1.0.1/scripts/install.ps1 | iex

Note: desktop builds are not notarized (macOS) or Authenticode-signed (Windows). On macOS, right-click → Open the first time (or xattr -dr com.apple.quarantine "/Applications/BOZKURT CODE.app"); on Windows, choose "More info → Run anyway" in SmartScreen. Verify downloads against SHA256SUMS. Third-party licences: THIRD_PARTY_LICENSES.md.

Changelog

A packaging release: no changes to the bz CLI, HTTP API v1, MCP tools or configuration keys.

Added

  • Signed in-app updates for the desktop app. Release builds now carry the Tauri updater public key and ship
    minisign-signed updater artifacts (*.sig) plus latest.json. On launch the desktop app checks
    releases/latest/download/latest.json, asks with a native dialog ("Install and restart" / "Later"), verifies the
    signature against the embedded key, installs and restarts (macOS .app, Windows NSIS, Linux AppImage; .deb/.rpm
    installs update through the package manager or a new download). Installs of 1.0.0 had no updater configured, so moving
    to 1.0.1 needs one manual download; later versions update in-app.
  • Release-signed Android builds. mobile.yml signs the APK (zipalign + apksigner, verified) and the AAB (jarsigner)
    with the project's release keystore, so later versions install over 1.0.1 without uninstalling. The unsigned and
    throwaway-key *-sideload.apk outputs are no longer published when the keystore is configured.

Changed

  • Mobile CI. Android builds no longer fail in setup-android (the legacy tools package is gone); without a
    release keystore (forks) an extra *-sideload.apk, signed with a throwaway key, is produced next to the unsigned
    APK/AAB. The iOS simulator build runs without APPLE_DEVELOPMENT_TEAM. mobile.yml can attach builds to an existing
    release (workflow_dispatch input release_tag).

Known limitations

  • macOS builds are not notarized and Windows installers are not Authenticode-signed (no paid certificates); expect a
    Gatekeeper / SmartScreen prompt on first launch. iOS ships as an unsigned simulator build only.

Full changelog: v1.0.0...v1.0.1

BOZKURT CODE v1.0.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 19:49

BOZKURT CODE v1.0.0

First public release of BOZKURT CODE — a local development environment manager: the bozkurtd daemon, the bz CLI, the bozkurt-mcp MCP server, a Tauri 2 desktop app and a mobile companion.

🌐 Website: https://cumabozkurt.github.io/bozkurt-code/

Downloads

Platform Desktop app CLI (bz, bozkurtd, bozkurt-mcp)
macOS (Apple Silicon) BOZKURT.CODE_1.0.0_aarch64.dmg bozkurt-cli-aarch64-apple-darwin.tar.gz
macOS (Intel) BOZKURT.CODE_1.0.0_x64.dmg bozkurt-cli-x86_64-apple-darwin.tar.gz
Windows x64 BOZKURT.CODE_1.0.0_x64-setup.exe / BOZKURT.CODE_1.0.0_x64_en-US.msi bozkurt-cli-x86_64-pc-windows-msvc.zip
Linux x64 .AppImage / .deb / .rpm (amd64 / x86_64) bozkurt-cli-x86_64-unknown-linux-gnu.tar.gz
Linux arm64 .AppImage / .deb / .rpm (aarch64 / arm64) bozkurt-cli-aarch64-unknown-linux-gnu.tar.gz

Mobile companion (LAN remote control):

File What it is
bozkurt-mobile-v1.0.0-app-universal-release-sideload.apk Android — install this one (sideload; signed with a build-time key, not a Play Store key)
bozkurt-mobile-v1.0.0-app-universal-release-unsigned.apk Android, unsigned (for re-signing with your own key)
bozkurt-mobile-v1.0.0-app-universal-release.aab Android App Bundle (unsigned, for Play Console)
bozkurt-mobile-v1.0.0-simulator.zip iOS simulator build (Apple Silicon Mac + Xcode); a signed device/App Store build needs Apple signing secrets

CLI quick install (verifies SHA256SUMS, no root needed):

curl -fsSL https://raw.githubusercontent.com/cumabozkurt/bozkurt-code/v1.0.0/scripts/install.sh | sh
irm https://raw.githubusercontent.com/cumabozkurt/bozkurt-code/v1.0.0/scripts/install.ps1 | iex

Note: the 1.0.0 desktop builds are not code-signed (no Apple notarization / Windows Authenticode yet) and ship without auto-updater artifacts (update by downloading a newer release). On macOS, right-click → Open the first time (or xattr -dr com.apple.quarantine "/Applications/BOZKURT CODE.app"); on Windows, choose "More info → Run anyway" in SmartScreen. Verify downloads against SHA256SUMS. Third-party licences: THIRD_PARTY_LICENSES.md.

Changelog

The first public release. There was no earlier tagged version, so everything built before it is listed here.

Highlights

  • bozkurtd daemon. axum HTTP API v1 on 127.0.0.1:7878 (see docs/API.md), WebSocket /events,
    service supervisor, background jobs, remote pairing for the mobile companion, bz share tunnels via cloudflared,
    import from other local tools, database management on MariaDB/PostgreSQL, doctor checks with one-click fixes, and a
    graceful POST /daemon/shutdown.
  • bz CLI. Every daemon feature from the terminal, with --json output, documented exit codes, daemon autostart,
    shell completions and bz mcp register for Claude Code, Cursor, VS Code, Windsurf, Gemini CLI and Codex.
  • bozkurt-mcp. stdio MCP server with 55 tools in four safety tiers; destructive and system tools return a preview
    until called with confirm: true.
  • Desktop app and mobile companion on the shared React UI, with English and Turkish translations.

Added

  • Workspace and licensing. Cargo workspace (bz-core, bz-net, bz-daemon, bz-cli, bz-mcp, desktop and mobile
    Tauri crates) and npm workspace (@bozkurt/ui, @bozkurt/desktop, @bozkurt/mobile). Dual license MIT OR Apache-2.0.
  • Reference docs. docs/ARCHITECTURE.md (goals, home layout, config, bozkurt.toml, core rules) and
    docs/API.md (HTTP API v1, types and events).
  • bz-core: paths and state. $BOZKURT_HOME layout with BOZKURT_HOME override, config.toml with validation
    (rejects HSTS-preloaded .dev/.app) and JSON merge-patch, per-project bozkurt.toml, and atomic state.json.
  • bz-core: upstream catalogs with a 6 h disk cache:
    • PHP: static-php.dev on macOS/Linux, windows.php.net on Windows.
    • Node.js (nodejs.org index, SHASUMS256 and release schedule), Bun (GitHub), Python (python-build-standalone) and
      Go (go.dev).
    • Composer (getcomposer.org).
    • EOL tagging for PHP and Python.
  • bz-core: runtimes. Install, uninstall and use with an atomic current/ link, shims in bin/ (POSIX sh and Windows
    cmd), and per-directory version resolution from project files.
  • bz-core: services. Catalogs, process specs and init:
    • Caddy (GitHub releases).
    • MariaDB: Linux x64 bintar and Windows x64 zip.
    • PostgreSQL (theseus-rs binaries).
    • Valkey as redis: Linux only.
    • Mailpit (SMTP 1025, UI 8025).
    • PHP-FPM pools, or php-cgi -b on Windows.
    • external status when a foreign process holds the port.
    • Aliases: mysql→mariadb, valkey→redis, postgresql→postgres.
  • bz-core: supervisor. Supervisor with restart-on-crash backoff, ring-buffer and file logs, a job system with
    progress events, and an event bus.
  • bz-core: project detection.
    • PHP: Laravel, Symfony, WordPress (incl. Bedrock), Drupal.
    • JavaScript: Next.js, Nuxt, Astro, SvelteKit, Remix/React Router, Vite, Express/Fastify/Koa. The package manager
      (npm, pnpm, yarn, bun) is detected too.
    • Python: Django, FastAPI, Flask.
    • Go, generic PHP and static sites.
  • bz-core: Caddyfile generation. php, proxy, static and app sites; wildcard subdomains and aliases; HTTPS redirect;
    per-site snippets. Snapshot-tested.
  • bz-net: DNS responder. UDP and TCP responder for *.<tld> → 127.0.0.1 / ::1, with live TLD changes.
  • bz-net: OS resolver plans.
    • macOS: /etc/resolver.
    • Linux: systemd-resolved, then NetworkManager dnsmasq, then hosts.
    • Windows: NRPT (needs port 53), then hosts.
  • bz-net: local CA. rcgen, ECDSA P-256, 10 years, key 0600. Leaf certificates last 825 days and are renewed within
    30 days of expiry, or on a SAN or CA change.
  • bz-net: trust plans. macOS login keychain, Windows CurrentUser\Root, Linux NSS databases (Chrome and Firefox
    profiles), plus an optional system store.
  • bz-net: ports, hosts and elevation. Port-owner lookup (PID and process name), a managed hosts-file block, and an
    elevation layer. Each elevated change is a named plan with backups and one prompt per admin block.
  • @bozkurt/ui: shared React UI.
    • Screens: Overview with Quick setup, Sites, Runtimes, Services, Logs, Doctor, Settings with the remote-pairing QR
      code, and Connect for mobile.
    • Jobs drawer, command palette (⌘K / Ctrl K), keyboard shortcuts and toasts.
    • Light, dark and system themes; complete English and Turkish translations.
    • Typed API client with WebSocket reconnect, and an in-memory mock backend.
  • Desktop app (Tauri 2).
    • Tray/menu-bar menu: status, Switch PHP/Node, start/stop all, palette, launch at login.
    • Starts the bozkurtd sidecar; bozkurt:// deep links; single instance; open in editor or terminal.
    • Bundles: dmg, msi/nsis, deb/rpm/AppImage.
  • Mobile companion (Tauri 2, iOS and Android). Pairing by QR code (bozkurt://pair?host=…&code=…) or manual entry,
    bearer token, bottom tab bar, demo mode.
  • Install scripts. scripts/install.sh (macOS/Linux) and scripts/install.ps1 (Windows) install the CLI binaries
    into $BOZKURT_HOME/bin with SHA-256 verification against SHA256SUMS, without root.
  • CI. rustfmt; clippy and tests (--locked) on Linux, macOS and Windows; Node typecheck and build; desktop cargo check
    with the sidecar overlay; mobile shell check; a repo-lint job (actionlint, shellcheck, PSScriptAnalyzer, JSON, Markdown
    links, version drift).
  • Release workflow. Draft release, CLI archives for 5 targets, Tauri bundles, SHA256SUMS, and optional
    macOS/Windows signing and notarization.
  • Mobile workflow. Android APK/AAB and iOS builds, signed when secrets are present.
  • Documentation. README (EN/TR), user guide (EN/TR), CLI and MCP references, comparison, roadmap, CONTRIBUTING,
    SECURITY and Code of Conduct.
  • Databases. GET|POST /services/{engine}/databases, DELETE /services/{engine}/databases/{name}; bz db list|create|drop and the db_* MCP tools.
  • Undo for OS changes. POST /dns/unconfigure (bz dns setup --undo) and POST /tls/untrust (bz trust --undo).

Security

  • Local API token. bozkurtd creates a per-install token in $BOZKURT_HOME/api-token (mode 0600). Clients without
    an allow-listed browser Origin must send it as Authorization: Bearer <token> (or X-Bozkurt-Token); bz and
    bozkurt-mcp read it automatically. Missing or wrong token → 401.
  • Origin and Host guard. Browser requests are accepted only from the packaged app's origins (the dev-server origins
    only with BOZKURT_DEV=1 or in debug builds) → otherwise 403. Mutating requests with a non-JSON Content-Type → 415.
    A Host other than 127.0.0.1/localhost/[::1] on the API port → 421 (DNS rebinding).
  • Caddyfile hardening. Sites bind to 127.0.0.1 and ::1 only unless lan_access = true; every value written to the
    Caddyfile is quoted so site fields cannot inject directives or blocks, and invalid site fields are rejected.
  • Downloads fail closed without a checksum. A download whose upstream publishes no checksum (static-php.dev PHP on
    macOS/Linux; Windows PHP, Go or cloudflared when the index drops its hash) fails with unverified_download (422)
    unless allowed once ("allow_unverified": true on POST /runtimes/{kind}/install, bz … install --allow-unverified, "Install anyway" in the app) or always (new config key allow_unverified, default false). The
    first allowed download is pinned by sha256 in state.json (download_pins); a later download that differs fails with
    checksum_mismatch. MCP has no bypass.
  • Pairing brute-force limits. Pairing codes are 8 digits (were 6). On top of 5 attempts per address per minute, all
    addres...
Read more