Repository navigation
Apra Fleet 0.4.3 -- deprecations and required upgrades #496
kumaakh
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Status: 0.4.3 is released. See the announcement: Apra Fleet v0.4.3 -- now available (#552). This post remains the detailed reference for the deprecations and required upgrades below.
1. Beads 1.3.0 is the required
bdversionfleet-sprint now targets beads (
bd) 1.3.0. Every fleet member that runs sprints -- the orchestrator box and every doer/reviewer clone -- must be on 1.3.0 before you launch a sprint with 0.4.3.bd version(expectbd version 1.3.0).bd prune/bd flattenfor reclaiming Dolt storage. We now document a periodic maintenance procedure:packages/apra-fleet-se/docs/beads-maintenance-playbook.md. Read the prerequisites before running it --bd flattenrewrites history with no shared ancestor, so every other clone must re-bootstrap afterward, and every member owner must have pushed first. There is no automated self-heal for this yet.2.
{{secure.NAME}}is deprecated -- use{{secret.NAME}}The credential-store placeholder is now spelled
{{secret.NAME}}everywhere: tool descriptions, docs, skills, PM prompts, the FAQ. (PR #495){{secure.NAME}}still works and resolves identically, but every use appends a[deprecated]line to the tool result and the fleet log. It will not hard-fail in 0.4.3; the removal window will be announced separately.apra-fleet authCLI acceptssecret.<name>/--secret;secure.<name>/--secureremain as deprecated aliases (notice on stderr).secure_credential_not_found/secure_credential_denied/secure_credential_expiredwere renamed tosecret_variable_not_found/secret_variable_denied/secret_variable_expiredwith no alias. Anything that switches onstructuredContent.reasonmust be updated. (No third-party consumers are known;apra-fleet-clientand fleet-sprint are already updated.)deploy.md, saved prompts, and sprint args needs updating:{{secure.->{{secret..npm testin apra-fleet now fails on the old spelling in docs/prompts; the same guard is not applied to target repos.docs/secret-variables.md. FAQ How do I pass secrets to fleet commands without the LLM seeing them? #237 has been updated.3.
better-sqlite3is no longer a dependencybetter-sqlite3and@types/better-sqlite3were removed frompackage.json(PR #494). Nothing loaded it at runtime -- the knowledge bank has used the builtinnode:sqlitesince the SEA binary could not load better-sqlite3's native addon.npm installno longer pulls the node-gyp/prebuild chain on any member OS.import 'better-sqlite3', that import will now fail. Usenode:sqlite(DatabaseSync) instead -- it is the only sqlite that works inside the SEA binary anyway.4. GitHub App: two new required permissions (Workflows, Actions)
If you use GitHub App mode (
setup_git_app+provision_vcs_authwithgithub_mode: github-app), 0.4.3 requests two App permissions earlier releases did not. PAT mode is unaffected.push,push+pr,admin,full(PR Auto-sprint [PASS]: fix/v05-stability-sync-and-stall #511). Without it GitHub rejects any push touching.github/workflows/**.push+pr(it was already onadmin/full) so agents can re-run failed CI jobs on their own PRs (PR fix(github-app): push+pr tokens may re-run CI jobs (actions: write) #541).Why this breaks an existing App:
provision_vcs_authrequests exactly the permission set of the chosengit_accesslevel and never silently drops one. If the App lacks any of them, the mint fails withToken mint failed: GitHub App <id> (installation <id>) is not granted one or more of the requested permissions [...](reason: deploy_failed). For fleet-sprint -- which mintspushfor sync andpush+prjust before raising the PR -- the typical symptom is a sprint that pushes its branch and then logs[Publish PR Skipped] ... Could not provision a push+pr credential ...instead of opening the PR.Action required (org owner/admin), before upgrading the server:
provision_vcs_authwithgit_access: "push+pr"on one member returnsok: trueandmetadata.permissionsincludesworkflowsandactions.Full per-level permission table and setup walkthrough: docs/github-app-setup.md.
5. Node.js 22.16+ and npm are required for fleet-se (sprints, supervisor, bd)
apra-fleet core -- the single-binary server, console, members, secrets, health -- needs no Node.js. But fleet-se -- the fleet-sprint engine, the fleet supervisor, and the beads task tracker
bd(installed via npm,bd1.3.0) -- requires Node.js 22.16 or later and npm.node --version(expect 22.16.0 or later) andnpm --version.--workflows noneinstalls the core without fleet-se, and Node.js/npm are not required.bd.What to do before upgrading
bdto 1.3.0 on every member.{{secure.and switch to{{secret.; fix any script that readssecure_credential_*reason codes.better-sqlite3, move it tonode:sqlite.Questions or something missing -- reply here.
All reactions