OverviewFilesCommitsIssuesDocsReleasesPeers

pear-git-v3 commits / a797126

Pass the seeder on the manual-trigger path too
I threaded vdriveSeeder through autoBuildFromPush and both push call sites but missed the build-release RPC, which is what `pgh deploy trigger` uses. A manually triggered build would therefore publish a drive without dropping the seeder's exclusive lock first, and without announcing the result — the same defect just fixed on the push path, still live on the other one. Found by accidentally triggering a build: `pgh deploy trigger <repo>` defaults to refs/heads/master, which for this repo is upstream without a ci.yaml, so it skipped — and reading why surfaced the missing wiring. Both buildAndPublish call sites now receive the seeder. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
a797126fc889c8f0cd409d4004cc596dea4eb8e3
by plankatron <fleeky@gmail.com> · 2026-08-25T00:25:48.000Z

Changed files (2) +5 -1

lib/handlers/releases.js +4 -0
……@@ -230,6 +230,10 @@ export function releaseHandlers (svc) {
230230 return buildAndPublish({
231231 sync: svc._sync,
232232 releaseManager: rm(),
233 // Manual triggers need the seeder too: without it a vdrive publish
234 // cannot drop the seeder's exclusive lock on the store, and the new
235 // drive is never announced. The push path threads this already.
236 vdriveSeeder: svc._vdriveSeeder,
233237 repo,
234238 ref,
235239 isTag: !!isTag,
package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "pear-git-v3",
3 "version": "0.1.230",
3 "version": "0.1.231",
44 "description": "P2P git forge \u2014 multi-writer issue/org/release/peer-mirror daemon. Built bottom-up after the failed v2.",
55 "type": "module",
66 "main": "index.js",